How hard would it be to have :term windows operate with "nowrap" ?

I find the ability to have a vim window operate as a terminal really useful (the :terminal command).  

The one thing I really find annoying about it is the fact that it wraps lines that are longer than the window width with a hard carriage return, so that if you go back and select text from the terminal, it contains carriage returns that were not actually present in the program output.  As far as I can tell, there are no settings to change that.  How hard would it be to add that capability?

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAJjaVfVHJd%2BbRY5BpuYfL0QgdUo34ShTufWuvVf5py0i51tcew%40mail.gmail.com.

Re: autocmds general usage

On Wednesday, April 1, 2026 at 10:43:09 AM UTC-4 Christopher wrote:

I have a general question about autocmd, how can I use it without always having invoke it by using ":" then loading the appropriate commands then finally the file to which I want it to apply or must I script it ?

I don't understand the question (what do you mean "use it" without "using ':'", etc.?), but:

The typical practice for autocommands is to put them in your vimrc (~/.vim/vimrc, etc.) or a local plugin (~/.vim/plugin/<name>.vim) so they are established during startup.

Some customizations don't required autocommands, though: if you're customizing the behavior of a particular filetype, then use an ftplugin, indent, or syntax script. (Or your filetype may already have knobs to tweak; see `:help :syn-file-remarks`, `:help ftplugin-docs`, `:help local-additions`, etc. Completing with `:help ft-<filetype><Ctrl-d>` is usually good too.)

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/75d80253-9b2f-414c-af30-6b8909714b86n%40googlegroups.com.

autocmds general usage

I have a general question about autocmd, how can I use it without always having invoke it by using ":" then loading the appropriate commands then finally the file to which I want it to apply or must I script it ?

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/8c22618b-c796-4dd8-ae79-e674df044fe6n%40googlegroups.com.

New Line Criteria ?

How do I get vim to show a file to display for example where there is /bin: place it on a new line but revert back to how it was before the file was loaded into vim ?  

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/b8d1d80d-e21d-41f8-b7d6-0e24c31df5d3n%40googlegroups.com.

Re: $VIMRC over .vimrc ?

On Friday, March 20, 2026 at 10:58:21 AM UTC-4 D. Ben Knoble wrote:

On Fri, Mar 20, 2026 at 9:58 AM Christopher <crestchr...@gmail.com> wrote:
>
>
>
> On Thursday, March 19, 2026 at 8:44:22 PM UTC-4 Marvin Renich wrote:
>
> * Christopher <crestchr...@gmail.com> [260319 19:14]:
> > On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mr...@renich.org> wrote:
> > > The user's vimrc file _must_ be one of the files listed above, unless
> > > you specify the -u option. The only way to specify the vimrc file in an
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> > > before (or while) starting vim.
> >
> > You mention, the only way to specify a vimrc in a environment variable; I
> > assume as in $MYVIMRC is to export VIMNT which is the source of your vimrc
> > file. If my vimrc file was located in the system path then that would be;
> > VIMINT=`/etc/vimrc and that would create the environment variable $MYVIMRC
> > ?
>
> You need to read carefully and for exact syntax and content:
>
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Remember that VIMINIT specifies an ex command to execute, not a file
> name. If you want to source a file using VIMINIT, you must specify the
> source command itself, not just the file name.
>
> Also, when testing this, know that :scriptnames is your friend.
>
> Also note that if your vimrc file is the system vimrc file (/etc/vimrc
> on some distributions, /etc/vim/vimrc on Debian), it is sufficient to
> use:
>
> VIMINIT=':' vim
>
> or
>
> export VIMINIT=':'
> vim
>
> as the system vimrc is sourced even if you specify a VIMINIT. Setting
> VIMINIT=':' simply disables reading of the user vimrc file, but not the
> system vimrc file. (':' is an empty ex command.)
>
> Finally, if you specify VIMINIT, MYVIMRC is _not_ set by vim.
>
> ...Marvin
>
>
> What do you mean by :scriptnames ?

":scriptnames" is an Ex command supported by Vim that announces what
scripts have been executed in the current session. (":help
:scriptnames").

> Within vim I run the command; VIMIT=: (colon) and that takes my system vimrc assigns it the variable $MYVIMRC or that has to be done after ?

I get the sense you may not be reading very carefully, but let me try
to clear up some confusion:

- "VIMINIT=: vim" is an example shell command that would disable
initializations from vimrc files other than the system vimrc.
(Notably, this does _not_ disable user-local plugins.)
- Vim will assign MYVIMRC if and when it finds and executes a user
vimrc. It never (AFAIK) assigns MYVIMRC to the path of the system
vimrc.
- The above point is moot if you set VIMINIT; then nothing sets MYVIMRC
- MYVIMRC is never _read_ by Vim to take any action (unless a plugin
or script uses it)

I wanted to clarify that it's now clear. In order to use the environment variable $MYVIMRC you must have a user; .vimrc file created, typically at the $HOME path for the installed nix version.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/0ab878b1-afba-4524-913b-5ffe79587c76n%40googlegroups.com.

Re: pattern syntax for match()

tim / christian

thank you.  both forms work as expected:  single and double quoted forms.  in all of my quoting permutations, i had been escaping the bar, also.

works fine, now.  many thanks.

On March 25, 2026 12:41:15 PM PDT, Christian Brabandt <cblists@256bit.org> wrote:

On Mi, 25 Mär 2026, Tim Chase wrote:

On 2026-03-25 12:01, S. Cowles wrote:
i would like to do the following operation:
	let m = match( "foo" , "foo\|beep" )
however, i get no match.  (m is (-1).)
what is the correct pattern syntax to enable this match?

Because they're strings, do you need to escape the "\", making it

  let m = match( "foo" , "foo\\|beep" )

Or a bit more readable, use single quotes instead.

Thanks,
Christian

--
scowles@sonic.net
+1 510 380 8661

Re: pattern syntax for match()

On Mi, 25 Mär 2026, Tim Chase wrote:

> On 2026-03-25 12:01, S. Cowles wrote:
> > i would like to do the following operation:
> > let m = match( "foo" , "foo\|beep" )
> > however, i get no match. (m is (-1).)
> > what is the correct pattern syntax to enable this match?
>
> Because they're strings, do you need to escape the "\", making it
>
> let m = match( "foo" , "foo\\|beep" )

Or a bit more readable, use single quotes instead.

Thanks,
Christian
--
Are we not men?

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/acQ6W0dcgdWjG1p2%40256bit.org.