You both make good arguments. This may be worth an exception after
all.
Regards,
Gary
--
--
You received this message from the "vim_dev" 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
On 2024-09-24, Nir Lichtman wrote:
> Very interesting, I actually noticed this behavior a couple of days ago and I
> wasn't sure why it specifically occurred with Vim, but this clears it up.
>
> Opened a PR to address this issue by changing the default value of bkc: #15739
If you are aware of 'bk
On 2024-06-17, Christian Brabandt wrote:
> If that is the case, I am fine with skipping. But I don't know how to detect
> that Vim is running in a Mingw/Msys environment.
My MINGW64 installation has a couple of environment variables that
you could test.
MSYSTEM=MINGW64
OSTYPE=msys
Regard
On 2024-06-02, Christian Brabandt wrote:
> On Sa, 01 Jun 2024, Gary Johnson wrote:
>
> > I would like to request that developers not leave calls to ch_log()
> > enabled in released code, that is, in code that has been committed
> > to the GitHub repo.
> >
> >
I would like to request that developers not leave calls to ch_log()
enabled in released code, that is, in code that has been committed
to the GitHub repo.
I just tried debugging some Vim code by sprinkling calls to ch_log()
in it. When I ran tail on the log file, I was inundated with log
messages
On 2024-05-30, Christian Brabandt wrote:
> On Di, 28 Mai 2024, Gary Johnson wrote:
>
> > I follow Vim development activity through the vim_dev mailing list
> > rather than at https://github.com/vim/vim/. That generally works
> > well, except that I seem to miss the o
On 2024-05-29, ElwinGao wrote:
> when I search text like this:
>
> 1. www.github.com
> 2. www.google.com
>
> ---
>
> current cursor(cursor type is block) on the first "w" in first line，and then I
> using "/" to sea
I follow Vim development activity through the vim_dev mailing list
rather than at https://github.com/vim/vim/. That generally works
well, except that I seem to miss the original postings of some
issues and/or PRs. I see responses, but not the original postings,
so I'm potentially missing postings
On 2024-05-13, Diego Viola wrote:
> Please consider doing a runtime switch to the XDG one when a ~/.config/vim
> directory exists.
>
> Currently the runtime switch happens when ~/.config/vim/vimrc exists, and
> that's fine.
>
> However, while testing #14757 yesterday, I ran into some issues when
On 2024-05-12, lkintact wrote:
> Steps to reproduce
>
> 1. Run gvim.exe --clean.
> 2. Execute :set showbreak=>.
> 3. Execute :set laststatus=2 to enable the status line.
> 4. Execute :set statusline=%v.
> 5. Type 1000ia to put 1000 letters "a" in the buffer. Note that the
> status line re
When 'breakindent' is set and the window width is less than
'textwidth', the gqap command reformats indented paragraphs to less
than 'textwidth'.
Steps to reproduce
1. Create a file containing a single paragraph of arbitrary text,
indented by one 8-space tab stop and formatted for a textwidt
On 2024-04-02, Christian Brabandt wrote:
> In any case, things are a bit in flow currently and we are not close to a
> release. So some potential fallout can be expected. I try not to break
> backwards compatibility intentionally, but of course I'd like Vim to be
> improved and fixed. Yes it might
On 2024-03-29, luukvbaal wrote:
> I can try, but are we making a decision solely for backward compatibility? Or
> can we consider which of the two old behaviors makes more sense for scrolling
> the viewport. Either the cursor position stays the same and only starts moving
> to be at the top/botline
On 2024-03-17, San wrote:
> @chrisbra
> Also i found another bug( or maybe its on purpose)
> When you only have /t( tab or indentation) without any text on a new line. And
> you navigate back to previous line and press delete button, the next line does
> not get deleted but the /t( tab or indentati
On 2024-03-15, Christian Brabandt wrote:
> we could just use XDG_CONFIG_HOME/vim as we use $HOME/.vim only if we find
> a XDG_CONFIG_HOME/vim/vimrc. But I would also put the viminfo in
> XDG_CONFIG_HOME/vim since if the user is using XDG_DIRS they don't want
> clutter in their HOME.
On 2024-03-06, ShinyNeonCalvin wrote:
> Steps to reproduce
>
> 1. Make a colorscheme file
> 2. Put it in the same folder as other colorschemes
>
> Expected behaviour
>
> At one time, I was able to have vim recognize a color scheme I made by just
> putting this code in the file and putting the
On 2024-03-05, Christian Brabandt wrote:
> Hm, thanks for your suggestion. I have mad a very quick patch here:
> chrisbra@fe4a04a
>
> This misses test so is not yet ready to be included, but you may want to try
> it
> out.
We should probably understand what Vim is doing now and why before
making
On 2024-02-20, tyler-suard-parker wrote:
> @chrisbra @zzzyxwvut I understand, I used Nano for years, despite Vim being
> the
> vastly superior editor, because Nano has the hotkeys right there on the
> screen,
> which makes it way easier to use. I know we can't do that with Vim, but just
> having
On 2024-02-09, luca.saccar...@saccarosium.com wrote:
> Hi all,
> I would like to make a proposal for decoupling the clipboard
> functionality from X11.
>
> I've study the code base for some time but I still need some help on
> where and how exactly do this.
>
> The problem
> ===
>
> Curr
On 2024-01-16, Britton Kerin wrote:
> The sequence 'vaw' (visual around word is how I think of it) does
> weird things depending on white space:
>
> * 'vaw' while on 'a' in 'foo bar' selects ' bar' (space followed by bar)
>
> * 'vaw' while on 'a' in 'foo bar ' (with trailing space) selects
>
On 2024-01-17, FEA-eng wrote:
Try this on the machines where syntax folding works and where it
doesn't while editing a file for which you expect it to work.
:verbose set foldmethod?
That should tell you where 'foldmethod' was last set and the value
it was set to.
Regards,
Gary
--
--
You
On 2024-01-08, Yegappan Lakshmanan wrote:
> Hi Gary,
>
> On Mon, Jan 8, 2024 at 12:14 PM Gary Johnson wrote:
>
> On 2024-01-07, Yegappan Lakshmanan wrote:
>
> > To demonstrate the use of the new matchbufline() function, I have
> created
> > the fo
On 2024-01-07, Yegappan Lakshmanan wrote:
> To demonstrate the use of the new matchbufline() function, I have created
> the following script. This does search text completion from the list of words
> in the current buffer. After typing a few letters in the "/" prompt, if you
> press
> Tab, it wi
On 2024-01-07, Danek Duvall wrote:
> I wanted to be able to set the colorscheme based on the terminal colors (and
> adapt to terminal color changes), but there was no mechanism where
> v:termrbgresp was reliably correctly set. This enhances TermResponse to
> deliver
> the type of response it got s
On 2024-01-07, Christian Brabandt wrote:
> I have made a few minor changes, which turned out to be even more involved:
>
> • Renamed those new groups to Added, Changed and Removed (I initially went
> with capitalizing the diffAdded to DiffAdded, but since hightlighting
> groups are not c
On 2024-01-04, Christian Brabandt wrote:
> Yeah also true. Whatever you do, you will choice wrong 🙈
I hadn't followed this discussion until just now when I did a git
commit and looked at the diff section. It is butt ugly and
unreadable.
I use Vim to look at diffs daily, mostly in diff mode but o
On 2023-12-26, Edwin Chan wrote:
> Steps to reproduce
>
> 1. Create a buffer with a single line of arbitrary text
> 2. Place the cursor anywhere on the line and perform any of the following
> actions:
> a. Press }: The cursor jumps to the end of the line
> b. Press {: The cursor unex
On 2023-12-20, zeertzjq wrote:
> And, some bytes in the file correspond to a multibyte char in latin-1
> encoding,
> so such a byte counts as two bytes.
I didn't understand that statement at first, but now I do. Thanks.
When Vim's 'encoding' is utf-8 and it reads a file it sees as having
a 'fil
On 2023-12-19, 3052 wrote:
> Steps to reproduce
>
> using this file (inside, not the zip):
>
> https://github.com/vim/vim/files/13720982/index_video_5_0_1.zip
>
> If I open the same file in GVIM and enter /mdat, enter, g, ctrl+g I get:
>
> Byte 2785
>
> Expected behaviour
>
> if I run this Go
On 2023-10-04, Darin Hensley wrote:
> I am compiling VIM in Ubuntu 20.04. I tried compiling it according to this
> doc.
> However, I can not get it to read the system file /etc/vim. It also does not
> read ~./vimrc and does not read ~/.vim/ (contains colors, pack, plugins, etc)
> and does not read
On 2023-10-01, Restorer wrote:
> Perhaps future codes can and should be grouped?
>
> The question is by what principle to group the messages.
> Is it worth making groups for each Vim command (function). Or should they be
> grouped by data types, or by Vim modes?
> In my opinion, a good startin
On 2023-09-28, SturkenSnure wrote:
> I'm having the same problem.
>
> The only solution I have found is to use a terminal emulator like rxvt.
> Otherwise, every other terminal emulator (gnome-terminal, konsole, kitty, etc)
> do the same thing.
>
> This is a really annoying feature. It should be p
On 2023-09-25, errael wrote:
> I thought it was supposed to work that way. It is handy to be able to
> scroll the two windows independently by just clicking and moving the
> mouse.
>
> I actually was using that feature today. I'd never know explicitly about it,
> and was surprised, but it
On 2023-09-25, zeertzjq wrote:
> Problem: 'scrollbind' doesn't work when scrolling inactive window.
> Solution: Call do_check_scrollbind() after scrolling inactive window.
I thought it was supposed to work that way. It _is_ handy to be
able to scroll the two windows independently by just clicking
On 2023-09-13, Ernie Rael wrote:
> Greetings,
>
> In a plugin I'm working on, when certain simple errors occur, I want to ring
> the bell, some kind of alert. A popup, use in some place in the plugin, is
> more
> than is needed.
>
> The closest thing I can find is
>
> call sound_playevent('
On 2023-08-19, Christian Brabandt wrote:
> Yes, probably should get vimball as an own filetype. And possibly also get rid
> of .vba as extension for vimball. It's been long gone and nowadays vimballs
> use
> the .vmb extension anyhow.
All of the vimballs I have from Chip Campbell use the .vba
ext
On 2023-07-29, partev wrote:
> closing this pull request. If you change your mind you can always run advpng
> -z
> -4 -i 400 $(find . -name '*.png')
>
> there are two more cases where 1.7 kB space saving is real and not impacted by
> filesystem block size.
What do you mean by that? How is the s
On 2023-07-27, partev wrote:
> I agree that doing only one .png file is maybe not worth doing, but
> re-compressing all of them saves 1760 bytes, which I think is worth it.
Except that, as Eric pointed out, it doesn't save any space at all.
$ ll *.png
-rw-rw-r-- 1 gary gary 454 Dec 7 20
As others have written, if you're using gvim, it should just work
because Vim is doing the copying and knows not to include the
listchars characters. But even if you're using vim in a terminal
such as xterm, it should also just work, because if Vim is properly
configured to do the copying, again i
On 2023-06-26, Enan Ajmain wrote:
> But out of curiosity, this isn't what OP was after, is it? Munif was
> looking to change the default QF behavior by opening the QF window under
> the current window. Your function, Gary, opens the file in QF entry in
> the previous window. They are different
On 2023-06-07, Munif Tanjim wrote:
> Might be that I'm misunderstanding the expected behavior.
>
> If it's not supposed to be opened under curwin, would it be possible to change
> the default behavior to open with WSP_BOT (instead of WSP_BELOW)?
I didn't like the default behavior, either, so I ad
On 2023-06-19, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > On 2023-06-15, Bram Moolenaar wrote:
> > > > On 2023-06-15, Bram Moolenaar wrote:
> > > > > > Help for :map- says that with , the right side of
> > > > > > a mappi
On 2023-06-15, Bram Moolenaar wrote:
> > On 2023-06-15, Bram Moolenaar wrote:
> > > > Help for :map- says that with , the right side of
> > > > a mapping will not be echoed on the command line, but messages from
> > > > the executed command are still given. This works with :nmap but not
> > > > wi
On 2023-06-15, Bram Moolenaar wrote:
> Patch 9.0.1634
> Problem:Message is cleared when removing mode message (Gary Johnson).
> Solution: Do not clear the command line after displaying a message.
> Files: src/message.c, src/testdir/test_messages.vim,
> sr
On 2023-06-15, Bram Moolenaar wrote:
> > Help for :map- says that with , the right side of
> > a mapping will not be echoed on the command line, but messages from
> > the executed command are still given. This works with :nmap but not
> > with :vmap. I would expect it to work with :vmap as well.
Help for :map- says that with , the right side of
a mapping will not be echoed on the command line, but messages from
the executed command are still given. This works with :nmap but not
with :vmap. I would expect it to work with :vmap as well.
Steps to reproduce
1. Put the following in a file,
On 2023-04-29, Dani Dickstein wrote:
> Currently the shortmess option matrix for search messages looks like this:
>
> Feature 'shortmess' setting
> +s+S +s-S -s-S -s+S ???
> "search hit TOP/BOTTOM, c
On 2023-04-05, Nick Jensen wrote:
> Yes it is: http://www.drchip.org/astronaut/vim/
That page exists, but all the links to his scripts fail with error
404.
Regards,
Gary
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replyin
There seem to be a couple of debug print statements left in
list_mappings() in map.c, so that when I execute
:verbose abbreviate dt
(I have an abbreviation "dt"), I see at the top of the output:
Seen modifyOtherKeys: true
Kitty keyboard protocol: Cleared
I discovered that these were
On 2023-03-15, user202729 wrote:
> I'm not sure if this is a bug or not.
>
> Basically, if we use bash, then the subprocesses does not inherit the values
> of
> $LINES environment variable...
>
> $ echo $LINES
> 100
> $ bash -c 'echo $LINES'
>
> $ bash -ic 'echo $LINES'
> 100
> $
>
> here, in
On 2023-02-27, Bram Moolenaar wrote:
> So, can this issue be closed, or should we change something in Vim?
> E.g. adding that :unlet command in the diff filetype plugin?
I think it could be closed, but it's not my issue. I don't think
there is anything to change in Vim. There are a few other GIT
On 2023-02-26, Gary Johnson wrote:
> On 2023-02-26, huang bin bin wrote:
> > Steps to reproduce
> >
> > 1.git config difftool = vimdiff ,
> > 2.use git difftool open vimdiff compare git index file .
> > 3. execute :r ! git diff or !git diff > newfile then you
On 2023-02-26, huang bin bin wrote:
> Steps to reproduce
>
> 1.git config difftool = vimdiff ,
> 2.use git difftool open vimdiff compare git index file .
> 3. execute :r ! git diff or !git diff > newfile then you will see bash get
> hung, it can't back to vim . yout will have to ctrl+z to back ter
I've noticed a problem when I have multiple tab pages open, each
containing two windows that are diff'd, and I execute :diffoff! or
:tabclose! in one of the tabs. Either one of those commands resets
the value of 'scrollopt' from "ver,jump,hor" to "ver,jump". The
problem is that 'scrollopt' is a g
On 2023-01-28, Matt Martini wrote:
> Gary,
>
> I (and others) are having the same issue with vim-nerdtree-tabs.
> It is fully described here: issue #102
>
> There is a function that when a tab is closed, checks if the last buffer is
> NERDTree.
> and if it is it closes/quits.
>
> It was using
On 2022-12-20, madjxatw wrote:
> This behavior is really annoying! Whether to insert a comment leader should be
> decided by user but not assumed by the editor. Most of the time when placing a
> short trailing comment, I don't want a comment continuation. At least o should
> be removed.
>From my v
On 2022-12-02, Gary Johnson wrote:
> I've submitted a bug report to the mintty project, issue #1189.
This doesn't seem to have been a bug in mintty, but mintty resolved
the conflict with xterm anyway in version 3.6.3, which is now the
latest version in Cygwin.
Regards,
Gary
On 2022-12-14, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > > > I've had an autocommand in my vimrc for quite some time that
> > > > I noticed recently was causing the following error message when
> > > > activated:
> > > >
> &
On 2022-12-14, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > I've had an autocommand in my vimrc for quite some time that
> > I noticed recently was causing the following error message when
> > activated:
> >
> > Error detected while processing Bu
I've had an autocommand in my vimrc for quite some time that
I noticed recently was causing the following error message when
activated:
Error detected while processing BufEnter Autocommands for "":
E1312: Not allowed to change the window layout in this autocmd
I performed a git bisect on
On 2022-12-02, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> [...]
>
> > > I assume that mintty can't handle the escape sequences that do work for
> > > xterm. To find out which one please use a log:
> > >
> > > vim -N -u NONE -i N
On 2022-12-02, Christopher Plewright wrote:
>
> ESC[4m is "set underline mode"
Thanks, but the sequence I'm seeing is ESC[?4m.
Regards,
Gary
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information,
On 2022-12-02, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > After updating to the latest Vim, 9.0.0984, and starting Vim in
> > a terminal without a file specified, the command line font was
> > extremely tiny. (I'd estimate the font size to be 4 points.) If
&
After updating to the latest Vim, 9.0.0984, and starting Vim in
a terminal without a file specified, the command line font was
extremely tiny. (I'd estimate the font size to be 4 points.) If
a file was opened from the command line, its font in the buffer was
also tiny. Subsequent commands typed
On 2022-11-15, Melker Österberg wrote:
> Steps to reproduce
>
> 1. > vim -u DEFAULTS -c "set autoindent"
>
> 2. Enter insert mode and paste the following with + (assuming that you
> have copied it to your clipboard register)
>
> foo
> bar
> baz
>
> 3.
On 2022-11-07, Jonathon wrote:
> This was recently merged to Neovim (neovim/neovim#14537). Are you interested
> in
> merging it to vim if I update this pull request?
I'd be interested in trying it out.
Regards,
Gary
--
--
You received this message from the "vim_dev" maillist.
Do not top-post
On 2022-11-05, Balki wrote:
> Problem: :compiler shellcheck does not work
> Solution: Add ' %' to makeprg to pass current file to shellcheck
The 'makeprg' set by compiler files generally does not include %.
If the user wishes to make the current file, then they supply the
% themselves.
Regards,
G
On 2022-10-29, Gary Johnson wrote:
> On 2022-10-29, Carl Ponder wrote:
> > Based on this posting
> > https://vim.fandom.com/wiki/Searching_for_expressions_which_include_slashes
> > I tried re-mapping the '/' in my ~/.vimrc
> >
> > command! -nargs=1 / le
On 2022-10-29, Carl Ponder wrote:
> Based on this posting
> https://vim.fandom.com/wiki/Searching_for_expressions_which_include_slashes
> I tried re-mapping the '/' in my ~/.vimrc
>
> command! -nargs=1 / let @/ = |set hlsearch
>
> but it didn't work.
That won't work because user-defined commands
On 2022-10-28, Bram Moolenaar wrote:
> Strange that this went missing. I'll add it now, please suggest a git
> command for more info on the commit if needed.
I understand your frustration with git. Here are a couple of
commands I use to examine commits.
To see the commit messages in a pager, in
On 2022-10-22, Prabir Shrestha wrote:
> JSON is a common format that is used when coding backend apis. Would be good
> if
> vim had first class support for formatting JSON so that we don't have to use
> external tool or website.
I don't use JSON a lot. What sort of formatting do you want that
th
I was trying to add a word to the internal word list with zG. The
status line indicated that the word was added, but it remained
highlighted as a bad word.
Steps to reproduce
1. $ cd ~/src/vim/vim # where latest clean build of Vim resides.
2. $ VIMRUNTIME=runtime vim -N -u NONE -i NONE -c 'set
On 2022-10-13, Bram Moolenaar wrote:
> I'm glad you could locate the source of the problem. Please try the
> patch below. How could we make a regression test for this?
I tested it in the cases that had failed before and they work fine
now. Thank you.
As for a regression test, I'll have to thi
On 2022-10-12, Gary Johnson wrote:
> I started noticing odd behavior from cscope recently, so I ran 'git
> bisect' and found the problem at this commit:
>
> $ git bisect good
> dc21552c9a83413a018a91e61649cc632929d6a1 is the firs
I started noticing odd behavior from cscope recently, so I ran 'git
bisect' and found the problem at this commit:
$ git bisect good
dc21552c9a83413a018a91e61649cc632929d6a1 is the first bad commit
commit dc21552c9a83413a018a91e61649cc632929d6a1
Author: Bram Moolenaar
Date: S
On 2022-10-08, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > > > > I seldom use gvim on Linux and even less often use :sh from gvim, so
> > > > > I didn't notice this until recently when projects and my workflow
> > > > > changed.
&
On 2022-10-04, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > > I seldom use gvim on Linux and even less often use :sh from gvim, so
> > > I didn't notice this until recently when projects and my workflow
> > > changed.
> > >
> > > When
On 2022-10-04, Bram Moolenaar wrote:
> Patch 9.0.0655
> Problem:passing modifier codes to a shell running in the GUI. (Gary
> Johnson)
> Solution: Include modifier codes into the key and drop the modifiers.
> Files: src/term.c, src/proto/term.pro, src/os_unix.
On 2022-10-03, Gary Johnson wrote:
> I seldom use gvim on Linux and even less often use :sh from gvim, so
> I didn't notice this until recently when projects and my workflow
> changed.
>
> When :sh is used in gvim to launch a shell, the backspace and ^U no
> longer work.
On 2022-10-03, Bram Moolenaar wrote:
> Patch 9.0.0653 (after 8.2.0260)
> Problem:BS and DEL do not work properly in an interacive shell. (Gary
> Johnson)
> Solution: Adjust the length for replaced codes.
> Files: src/term.c, src/proto/term.pro, src/os_unix.c,
I seldom use gvim on Linux and even less often use :sh from gvim, so
I didn't notice this until recently when projects and my workflow
changed.
When :sh is used in gvim to launch a shell, the backspace and ^U no
longer work. Instead of backspacing or clearing the line, each just
puts gibberish in
I seldom use gvim on Linux and even less often use :sh from gvim, so
I didn't notice this until recently when projects and my workflow
changed.
When :sh is used in gvim to launch a shell, the backspace and ^U no
longer work. Instead of backspacing or clearing the line, each just
puts gibberish in
On 2022-08-23, Ahnaf Al Nafis wrote:
> You mswin cannot be activated by default in Linux.
Why do you think that? The OP explicitly sourced
$VIMRUNTIME/mswin.vim in their vimrc. When I source that file in
gvim on my Ubuntu 20.04 system, Ctrl-A, Ctrl-C and Ctrl-V behave as
they would on Windows.
On 2022-08-18, Ernie Rael wrote:
> On the voting page I see:
>
>5 92 improve diff mode: automatic refresh, better merge support
>...
>11 72 add diff/merge capability for git, mercurial et al.
>
> I don't understand the intent of item 11. For example, there's the
> plugin
>
> https
On 2022-08-17, aohan237 wrote:
> @chrisbra maybe the way git mergetool use vimdiff cause this.
>
> @vim-ml 's cmd solution goes right. maybe i should ask git for an answer,
> there
> is no doc on this feature
I don't know whether you saw my earlier, lengthy reply to Chris, but
that answered the
On 2022-08-17, Christian Brabandt wrote:
> I wonder, if this is caused by the recent changes in git release 2.37 on how
> vimdiff is called https://github.com/git/git/blob/v2.37.0/Documentation/
> RelNotes/2.37.0.txt
I wonder. I'm still running git 2.26.2. If, from the Vim instance
running the
On 2022-08-17, Christian Brabandt wrote:
> most likely, diff mode is enabled after the vim has completely started up (and
> after .vimrc) is read. Run it interactively using :echo &diff or in a VimEnter
> autocommand. I don't think this is a bug here.
Something funny is going on, though. When I t
On 2022-08-11, Brandon Richardson wrote:
> Hello all,
>
> I've been prototyping some alternative commands to :tselect and :tjump and I'm
> looking to get a bit of feedback from the community on whether this
> functionality is something worth introducing into the core project. This
> functionality
On 2022-07-10, haron13-2019 wrote:
> When skimming over documentation it is easy to erroneously believe one can use
> ":3mat" command - see my recent bug report #10690 instantly closed by
> @chrisbra
>
>
> Thinking about it a bit, may be this is good idea to officially remove ":3mat"
> from
I'm not sure this is bug, but it's not what I expect and I don't
know of a workaround.
I often use the Fugitive command ":Git difftool -y" to open a set of
tabs, each one containing a diff of the working tree version of
a file with some other version of that file. I sometimes use
a command such a
On 2022-06-24, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > I've noticed for a while when diffing two versions of a file that
> > the two windows sometimes get out of sync. I created and attached
> > two files that exhibit this problem. For this example, I ra
I've noticed for a while when diffing two versions of a file that
the two windows sometimes get out of sync. I created and attached
two files that exhibit this problem. For this example, I ran vim
version 8.2.5154 in an 80x24 xterm.
Steps to reproduce
1. Save the attached files to disk.
2. St
On 2022-06-03, Clément Bœsch wrote:
>>One person's magic incantation is another person's flexible
>>solution.
>>
>>I tried such a solution for a while, and also tried Dan Church's
>>shitespace.vim plugin, but neither did quite what I wanted, so
>>I wrote my own plugin so that I
On 2022-06-03, Clément Bœsch wrote:
> If we want to highlight EOL whitespaces, we currently have to rely
> on magic incantations such as:
>
> highlight WhitespaceEOL ctermbg=red
> match WhitespaceEOL /\\\@ augroup winenter_whitespaceeol
> autocmd!
> autocmd WinEnter * match WhiteSpaceEOL /
On 2022-05-30, kaymvoit wrote:
> Steps to reproduce
>
> This was observed in a SpectrumScale storage with CentOS.
> Vim warns of a read only file, for a file with mode despite GPFS ACL via
> NFSv4 ACLs grants full access.
>
> 1. Create file with mode
> 2. Grand full access via (NFSv4)
On 2022-05-22, Terry Greeniaus wrote:
> If I came across as confrontational I apologize. I am comforted to
> know that I will only have to keep my .vimrc up to date rather
> than carry around other files with me as well.
> @vim-ml, I find it odd to say it's a fix when the behaviour for as
> long
On 2022-05-21, Terry Greeniaus wrote:
> Seriously, practically nobody ever wants this behaviour. It's just
> not how anybody ever comments code. Changing the default behaviour
> in favor of the 3 people that do this vs. the 15 million people
> that don't is... questionable.
Really? Both the Linux
On 2022-05-21, Kato wrote:
> @ Gary (sorry, I don't know how to reply well to vim-ml)
No problem. I don't know how to reply properly to both the list and
the forum from the list, either, so I reply to both and live with
the duplicate messages in the list.
> Thanks for pointing that out.
> WSL u
Several years ago, someone posted an experimental plugin for
formatting paragraphs that would adjust the lengths of all the lines
so that the right margin would be less ragged than the usual
formatting algorithms produced.
For example, that first paragraph is formatted by Vim with its
normal forma
On 2022-05-21, ichizok wrote:
> And, in f_has(),
>
> #if (defined(UNIX) || defined(VMS)) \
>
> && (!defined(MACOS_X) || defined(HAVE_CONFIG_H)) \
>
> && defined(HAVE_SYS_UTSNAME_H)
>
> WSL is on Linux so I think all need is checking only #if defined(__linux__) &&
> defined(HAVE_SYS_UT
1 - 100 din 922 matches
Mail list logo
