On Sun, Sep 03, 2023 at 05:33:22AM -0700, Ron Aaron wrote:
> I was just given a bug report for a new version of my syntax file, and the
> problem is that a syntax keyword with a lone '[' doesn't work (it causes an
> error message E789)
See ":help E789":
<
On Mon, Apr 10, 2023 at 09:29:52AM +0200, Tony Mechelynck wrote:
> On Sun, Apr 9, 2023 at 11:02 PM Bram Moolenaar wrote:
> >
> >
> > Tony wrote:
> >
> > > Recently (but I'm not sure when) my supposedly Motif gvim started
> > > getting compiled without GUI. Examination of the config log showed the
On Wed, Oct 05, 2022 at 08:27:30AM -0400, Marvin Renich wrote:
> SGTM. I don't really have an opinion here. Perhaps a preference for
> "normal" to continue to not have support for external (non-vim)
> scripting languages; put them all in "huge".
>
> For the Debian maintainers (Is that just you,
On Tue, Aug 16, 2022 at 02:28:29PM -0500, tooth pik wrote:
> i just upgraded my opensuse and am struggling to get the proper nvidia driver
> installed -- doo dah
>
> i can't tell if my inability to build vim (no such file stropts.h) is because
> of my upgrade or a problem with patch 9.0.0220, the
On Sun, Jul 31, 2022, 20:54 Yegappan Lakshmanan wrote:
> Hi,
>
> Is there an official Ubuntu/Debian Vim 9 package? I see only
> old versions of Vim in the following pages:
>
> https://packages.ubuntu.com/search?keywords=vim
> https://packages.debian.org/search?keywords=vim
>
> Note that I know h
On Mon, Jun 13, 2022 at 09:43:20PM +0100, Bram Moolenaar wrote:
>
> Patch 8.2.5084
> Problem:When the GUI shows a dialog tests get stuck.
> Solution: Add the --gui-dialog-file argument.
> Files: runtime/doc/starting.txt, src/Make_mvc.mak, src/gui.c, src/main.c,
> src/message
put_view() only stores the fold information if "bt_normal() ||
bt_help()" is true. Since bt_normal() excludes any buffers where
'buftype' is set, this prevents fold info being stored for
buftype=acwrite.
I think storing the folds would make sense for this type of buffer.
This also makes me wonder
On Wed, May 04, 2022 at 01:28:45PM +0100, Bram Moolenaar wrote:
> Apparently using the $NoDefaultCurrentDirectoryInExePath environment
> variable is the standard way how later MS-Windows "solved" this. So Vim
> should respect it.
Ah, I was missing the bit that $NoDefaultCurrentDirectoryInExePath
On Tue, May 03, 2022 at 11:03:11AM +0100, Bram Moolenaar wrote:
>
> Patch 8.2.4860
> Problem:MS-Windows: always uses current directory for executables.
> Solution: Check the NoDefaultCurrentDirectoryInExePath environment variable.
> (Yasuhiro Matsumoto, closes #10341)
> Files:
On Thu, Apr 21, 2022 at 03:21:41PM -0700, Hisashi T Fujinaka wrote:
> On Thu, 21 Apr 2022, Bram Moolenaar wrote:
> > Yes, that makes sense, the functions were added in that patch.
> >
> > What I don't understand is why the header file isn't found. On my
> > system the file included from gui_gtk_x
On Sat, Mar 12, 2022 at 06:40:48PM +, Bram Moolenaar wrote:
> James McCoy wrote:
> > > Is there a good reason to not want the Motif version, or does this just
> > > require some encouragement for someone to setup the packages?
> >
> > Since people do seem to s
On Sat, Mar 12, 2022 at 10:59:57AM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > > > Patch 8.2.4527
> > > > Problem:The Athena GUI is old and does not work well.
> > > > Solution: Remove the Athena GUI from c
On Tue, Mar 08, 2022 at 03:07:02PM +, Bram Moolenaar wrote:
>
> I wrote:
>
> > Patch 8.2.4527
> > Problem:The Athena GUI is old and does not work well.
> > Solution: Remove the Athena GUI from configure to find out who still wants
> > support for this GUI.
> > Files: sr
On Fri, Dec 24, 2021 at 07:16:35AM -0800, Yegappan Lakshmanan wrote:
> Hi all,
>
> When a PR is updated more than once and if the Github actions are in
> progress for the previous PR update, then the Github actions are triggered
> one more time and the previous action run is not aborted. This work
On Sun, Dec 05, 2021 at 08:17:43PM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sun, Dec 05, 2021 at 07:11:00PM +, Bram Moolenaar wrote:
> > >
> > > Patch 8.2.3748 (after 8.2.3747)
> > > Problem:Giving an error for an empty sig
On Sun, Dec 05, 2021 at 07:11:00PM +, Bram Moolenaar wrote:
>
> Patch 8.2.3748 (after 8.2.3747)
> Problem:Giving an error for an empty sign argument breaks a plugin.
> Solution: Do not give an error.
> Files: src/sign.c, src/errors.h, src/testdir/test_signs.vim
Since the error has
On Sun, Dec 05, 2021 at 06:38:39PM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > Why? That complicates the plugin code the same way as dealing with this
> > patch already would. Whether a certain attribute is being defined or
> > not by the plugi
On Sun, Dec 05, 2021 at 05:43:17PM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sun, Dec 05, 2021 at 01:03:15PM +, Bram Moolenaar wrote:
> > >
> > > Patch 8.2.3743
> > > Problem:":sign" can add a highlight group wi
On Sun, Dec 05, 2021 at 01:03:15PM +, Bram Moolenaar wrote:
>
> Patch 8.2.3743
> Problem:":sign" can add a highlight group without a name.
> Solution: Give an error if the group name is missing. (closes #9280)
> Files: src/sign.c, src/errors.h, src/testdir/test_signs.vim
This remov
On Sun, Oct 17, 2021 at 02:13:32PM +0100, Bram Moolenaar wrote:
> *** ../vim-8.2.3527/runtime/doc/insert.txt2021-10-16 15:41:25.378336694
> +0100
> --- runtime/doc/insert.txt2021-10-17 13:36:08.557348706 +0100
> ***
> *** 855,860
> --- 842,902
> [‥]
> +
> + func
On Thu, May 06, 2021 at 12:45:21AM +0200, Dominique Pellé wrote:
> Hi
>
> I noticed that running a vim command such as...
>
>:g/./d
>
> ... was slow with a large number of lines, whereas it used to
> be reasonably fast. It e.g. takes ~7 seconds with "only"
> 5000 lines using:
>
> $ yes | n
On Sat, Mar 06, 2021 at 11:39:14AM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > Shouldn't the tests use CheckNotRoot() so they're skipped?
>
> I've been wondering what the best approach is:
> - Just let the tests fail, tell the user th
Shouldn't the tests use CheckNotRoot() so they're skipped?
On Fri, Mar 5, 2021, 14:48 Bram Moolenaar wrote:
>
> Patch 8.2.2570
> Problem:Tests fail when run as root.
> Solution: Add a comment mentioning the expected failure. (issue #7919)
> Files: src/testdir/test_edit.vim, src/testdi
On Sun, Feb 14, 2021 at 04:34:20PM +0100, Bram Moolenaar wrote:
> This is where it runs into the problem: the size should be zero.
> Since it's OK when the later statements are changed, I suspect that the
> "isn_arg.number" value is overwritten when generating one of the later
> statements. Since
On Sun, Feb 14, 2021 at 12:58:03PM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sat, Feb 13, 2021 at 04:23:02PM -0500, James McCoy wrote:
> > > On Sat, Feb 13, 2021 at 07:13:35PM +0100, Bram Moolenaar wrote:
> > > >
> > >
On Sat, Feb 13, 2021 at 04:23:02PM -0500, James McCoy wrote:
> On Sat, Feb 13, 2021 at 07:13:35PM +0100, Bram Moolenaar wrote:
> >
> > Somehow the Travis tests run fail for s390:
> > https://travis-ci.com/github/vim/vim/builds/217016917
> >
> > I do not see
On Sat, Feb 13, 2021 at 07:13:35PM +0100, Bram Moolenaar wrote:
>
> Somehow the Travis tests run fail for s390:
> https://travis-ci.com/github/vim/vim/builds/217016917
>
> I do not see this failure on other systems and valgrind and ASAN also do
> not report a problem.
>
> Does anyone have an ide
On Sun, Jan 31, 2021 at 04:46:51PM +0100, Bram Moolenaar wrote:
>
> Patch 8.2.2439
> Problem:Not easy to figure out what packages to get when installing Vim on
> a new Ubuntu system.
> Solution: Mention explicit commands that are easy to follow.
> Files: src/INSTALL
>
>
>
On Thu, Jan 21, 2021, 16:54 Bram Moolenaar wrote:
>
> Patch 8.2.2389
> Problem:Test failure on a few systems.
> Solution: Avoid that "char" value is negative.
> Files: src/vim9compile.c, src/vim9execute.c, src/vim9.h
>
>
> *** ../vim-8.2.2388/src/vim9compile.c 2021-01-21 20:21:24.240
On Tue, Nov 24, 2020 at 10:30:42AM +0100, Bram Moolenaar wrote:
>
> Christian wrote:
>
> > On Mo, 23 Nov 2020, Yegappan Lakshmanan wrote:
> >
> > > The Travis CI builds are very slow for the last month or so.
> > > It looks like the total number of parallel Linux builds for all
> > > the open so
On Thu, Oct 22, 2020, 21:39 Charles Campbell wrote:
> I confess that I'm not a git master. It'd be a help if you could send
> me a patch instead of a commit which I don't use
>
If you append ".diff" to a pull request URL, you get a diff you can
download. For example, https://github.com/vim/vim
On Wed, Jul 15, 2020 at 02:25:40PM +0200, Bram Moolenaar wrote:
> To make this work with a double quoted string, we don't have much choice
> but to disallow double quoted comments.
Just where vim9script is being used or everywhere?
> Vim has always supported double quoted comments, disallowing th
On Wed, May 6, 2020, 14:17 Tony Mechelynck
wrote:
> After upgrading to openSUSE 15.2 Beta including gcc 7.5.0 and GTK2
> 2.24.32 I get the warnings below at "make reconfig" in every module in
> all builds except Tiny and Small (don't hold your breath, it is a long
> quote even for a single Normal
On Sun, Mar 15, 2020, 12:19 Yegappan Lakshmanan wrote:
> I think, even in non-gui builds, some of the code path (e.g. clipboard)
> depend on the DISPLAY being set.
>
> I don't know whether this change is relevant to enabling the s390 builds.
> This change should be reverted as this reduces the co
On Sat, Feb 22, 2020 at 04:56:26PM -0500, James McCoy wrote:
> On Sat, Feb 22, 2020 at 09:21:56PM +0100, Bram Moolenaar wrote:
> >
> > James McCoy wrote:
> >
> > > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar wrote:
> > > >
> >
On Sat, Feb 22, 2020 at 09:21:56PM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar wrote:
> > >
> > > Dominique wrote:
> > >
> > > > At https://buildd.debian.org/status/package
On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar wrote:
>
>
> Dominique wrote:
>
> > At https://buildd.debian.org/status/package.php?p=vim
> > I noticed this test failure on hppa architecture:
> >
> > Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
> > No write since last chang
On Mon, Nov 4, 2019, 05:28 Bram Moolenaar wrote:
>
> > On Sun, Nov 03, 2019 at 09:20:20PM +0100, Bram Moolenaar wrote:
> > >
> > > Christian wrote:
> > >
> > > > On So, 03 Nov 2019, Bram Moolenaar wrote:
> > > >
> > > > > Right, "make vimtags" doesn't work. I'm not sure how widespread
> "type"
>
On Sun, Nov 03, 2019 at 09:20:20PM +0100, Bram Moolenaar wrote:
>
> Christian wrote:
>
> > On So, 03 Nov 2019, Bram Moolenaar wrote:
> >
> > > Right, "make vimtags" doesn't work. I'm not sure how widespread "type"
> > > is, I think "which" should be safer.
> >
> > type or command -v is the co
On Fri, Oct 25, 2019 at 09:54:33AM +, Sihera Andre wrote:
> On 25/10/2019 18:24, Christian Brabandt wrote:
> > On Fr, 25 Okt 2019, Sihera Andre wrote:
> >> I think there should be another debate enabling .viminfo to be a symlink
> >> and giving computer professionals the ability to manage their
On Tue, Aug 20, 2019, 09:30 Christian Brabandt wrote:
>
> On Di, 20 Aug 2019, Zdenek Dohnal wrote:
>
> > Hi all,
> >
> > I found out there is Vimx symlink to gvim binary in my Vim package in
> Fedora.
> >
> > Does anyone know what Vimx is/was? What behavior did it have?
> >
> > I see from man pag
On Thu, Jun 13, 2019, 10:43 Paul Jolly wrote:
> Hi all,
>
> I'd like to propose a version() function (or variable I guess?) that
> returns a string that is the semver version of Vim, i.e. v8.1.1518
>
Sounds like you're looking for the v:version variable.
Cheers,
James
>
--
--
You received t
On Tue, May 07, 2019 at 09:49:08PM +0200, Bram Moolenaar wrote:
>
> Patch 8.1.1290
> Problem:.hgignore and .gitignore are either distributed or in git, not
> both.
> Solution: Add .gitignore to the distribution and .hgignore to git. Update
> the entries. (Christian B
Since +autocmd was graduated, running a vim built with small/tiny
features will attempt to perform filetype detection. This fails loudly
because there is no +eval.
$ ./src/vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Feb 17 2019 22:20:05)
Included patches: 1-946
Compiled by jamessan
On Fri, Feb 15, 2019, 11:13 Gary Johnson On 2019-02-15, Bram Moolenaar wrote:
> > Gary Johnson wrote:
> >
> > > On 2019-02-14, Gary Johnson wrote:
> > > > On 2019-02-14, Paul wrote:
> > > > > ":" normally scrolls through command history. However, after
> > > > > I pipe the buffer to less, that no
On Fri, Feb 8, 2019, 11:00 Bram Moolenaar
> Ozaki Kiichi wrote:
>
> > It need remove the following.
> >
> > --- a/src/testdir/test_functions.vim
> > +++ b/src/testdir/test_functions.vim
> > @@ -1237,7 +1237,6 @@ func Test_platform_name()
> >if has('unix') && executable('uname')
> > let un
On Sun, Jan 27, 2019 at 02:29:51PM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > filetype.vim contains the following:
> >
> > 485 au BufNewFile,BufRead *.comcall
> > dist#ft#BindzoneCheck('dcl')¶
> > …
> &g
Hi,
filetype.vim contains the following:
485 au BufNewFile,BufRead *.comcall
dist#ft#BindzoneCheck('dcl')¶
…
1954 au BufNewFile,BufRead
*/etc/apache2/*.conf*,*/etc/apache2/conf.*/*,*/etc/apache2/mods-*/*,*/etc/apache2/sites-*/*,*/etc/httpd/conf.d/*.conf*
I'm seeing another test failure in Debian's build environment, which
seems to again be related to vim not running attached to a tty. I've
been seeing this since at least 8.1.0549 and the below run is with
8.1.0687.
This line
call feedkeys("ix\", 'tnix')
in Test_edit_forbidden() gets stuck w
On Thu, Dec 06, 2018 at 07:14:08PM -0800, Ben Fritz wrote:
> On Wednesday, December 5, 2018 at 9:44:30 AM UTC-6, jonshouse1 wrote:
> > Unfortunately people are still unhappy, partly because it seems there are
> > many people who do not use a user specific vimrc file and simply used the
> > system
On Wed, Dec 05, 2018 at 09:28:05AM -0800, zdoh...@redhat.com wrote:
> I looked into Vim's Makefile and I found out binary stripping happens
> during the built, which causes missing debuginfo data in the end of
> the build.
> Would someone mind telling me if there a reason why stripping is done?
> I
On Mon, Nov 26, 2018 at 11:55:14AM +, 'Jonathon Fernyhough' via vim_dev
wrote:
> On 26/11/2018 10:54, Christian Brabandt wrote:
> > On Mo, 26 Nov 2018, Christian Brabandt wrote:
> >> This looks very similar to the crash posted here:
> >> https://github.com/vim/vim/pull/2107#issuecomment-418816
On Sun, Nov 25, 2018 at 07:19:52AM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Thu, Sep 13, 2018 at 01:11:44PM +0200, Christian Brabandt wrote:
> > >
> > > On Do, 13 Sep 2018, 'Jonathon Fernyhough' via vim_use wrote:
> > >
&
On Thu, Sep 13, 2018 at 01:11:44PM +0200, Christian Brabandt wrote:
>
> On Do, 13 Sep 2018, 'Jonathon Fernyhough' via vim_use wrote:
>
> > On 13/09/2018 10:14, Christian Brabandt wrote:
> > > Are you sure this version includes the patch for 8.1.349? I am a bit
> > > confused because of the versi
I've been running into various, non-deterministic issues (segfaults and
vim just "disappearing") trying to update the Debian package. I think
the latter is due to the infinite recursion in the attached backtrace.
In this particular case, I was running the tests with ASAN enabled
(trying to get mo
On Sun, Nov 04, 2018 at 08:09:10PM +0100, Christian Brabandt wrote:
>
> On So, 04 Nov 2018, Bram Moolenaar wrote:
>
> > + else if (STRLEN(p_hlg) >= 1 && *p_hlg == 'C')
>
> James mentioned[¹], that this might be overly eager.
This isn't doing a case-insensitive comparison, so it _should_ b
On Tue, Aug 21, 2018 at 09:02:42PM -0400, James McCoy wrote:
> On Tue, Aug 21, 2018 at 08:29:09PM +0200, Bram Moolenaar wrote:
> > *** ../vim-8.1.0312/src/testdir/test_swap.vim 2018-05-12
> > 15:57:33.0 +0200
> > --- src/testdir/test_swap.vim 2018-08-
On Wed, Aug 22, 2018 at 03:12:34AM +0200, Elimar Riesebieter wrote:
> Hi all,
>
> compiling vim 8.1.0315 on arch powerpc gives the following failure:
>
> From test_cscope.vim:
> Found errors in Test_cscope_add_dir():
> Caught exception in Test_cscope_add_dir(): Vim(cscope):E563:
> stat(/source/v
On Tue, Aug 21, 2018 at 08:29:09PM +0200, Bram Moolenaar wrote:
> *** ../vim-8.1.0312/src/testdir/test_swap.vim 2018-05-12 15:57:33.0
> +0200
> --- src/testdir/test_swap.vim 2018-08-21 20:18:23.395917660 +0200
> ***
> *** 97,99
> --- 97,133
> set directory&
>
On Wed, Aug 08, 2018 at 06:01:50PM -0700, h_east wrote:
> Hi,
>
> 2018-8-9(Thu) 9:22:13 UTC+9 yega...@gmail.com:
> > Hi all,
> >
> > The 'inccommand' option in Neovim allows a user to perform
> > live substitution. When you type a :substitute command, the
> > document is modified live. A demonstr
On Mon, Jun 25, 2018 at 12:06:15AM +0200, Bram Moolenaar wrote:
>
> James McCoy wrote:
> > eval_expr_to_bool() handles numbers just fine. Why make supplying a
> > number for the skip argument a hard error instead of simply evaluating
> > it to a boolean?
> >
>
On Sun, Jun 24, 2018 at 10:21:10PM +0200, Christian Brabandt wrote:
>
> On So, 24 Jun 2018, Tony Mechelynck wrote:
>
> > At startup from a handcoded Session.vim I get this error (which I
> > didn't get before with the same session script)
> >
> > Error detected while processing function 24_Highl
On Sun, May 13, 2018, 10:56 Ken Takata wrote:
> Hi Bram,
>
> 2018/5/13 Sun 23:00:29 UTC+9 Bram Moolenaar wrote:
> > Patch 8.0.1832
> > Problem:Cannot use :unlet for an environment variable.
> > Solution: Make it work. Use unsetenv() if available. (Ken Takata,
> > closes #2855)
On Thu, Apr 19, 2018 at 02:11:45PM +0200, Dominique Pellé wrote:
> I'm with Bram here. We'll end up having b_str[] on Linux & macOS
> and b_str[1] on more exotic platforms (e.g. HPUX compiler). There might
> subtle differences in behavior somewhere as a result, and since we
> mostly test on platfo
On Sun, Apr 15, 2018 at 02:32:14PM +0200, Dominique Pellé wrote:
> Bram Moolenaar wrote:
>
> > Hello Vimmers,
> >
> > For a long time Vim code was made to be compiled with ANSI C (also known
> > as C89 and ISO C90). This means it can also be compiled on very old
> > systems. And since it wasn't
On Mon, Mar 12, 2018 at 11:21:55PM +0100, Christian Brabandt wrote:
> With vartabs:
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Mar 12 2018 23:10:47)
> Included patches: 1-1600
> Extra patches: variable tabstops
> Compiled by Christian Brabandt
> Huge version without GUI. Features included (+)
On Tue, Mar 6, 2018, 10:50 Christian Brabandt wrote:
> Bram,
> There was a problem about pasting special terminal chars reported at
> http://seclists.org/oss-sec/2018/q1/213
>
> Initially I thought that bracketed-paste mode will prevent such things,
> but it seems this still works. Is there anyth
On Fri, Jan 05, 2018 at 01:22:52AM -0800, Ni Va wrote:
> set luadll = "lua53.dll"
> set pythondll = "python27.dll"
> set pythonthreedll = "python36.dll"
> set rubydll= "x64-msvcrt-ruby240.dll"
First, you can't have whitespace around the ‘=’ when setting an option.
Second, Vim
On Nov 17, 2017 01:53, "Dominique Pellé" wrote:
Bram Moolenaar wrote:
> Travis reported an error found by ASAN in test_terminal.
> https://travis-ci.org/vim/vim/builds/302986836
> It looks like this:
>
> ==18767== ERROR: AddressSanitizer: heap-use-after-free on address
0x606e00061740 at pc 0x75a
On Thu, Nov 02, 2017 at 04:03:32PM -0700, Gary Johnson wrote:
> I opened an xterm and dragged it to the full width of my two
> monitors.
>
> $ echo $LINES $COLUMNS
> 50 370
Vim must not be detecting that your terminal can support newer mouse
addressing modes like urxvt or sgr. See :help
On Thu, Nov 02, 2017 at 06:40:35AM +0100, Dominique Pellé wrote:
> Debian builds on many platforms which is useful
> to have a look at. It's currently using vim-8.0.1226.
> Glancing at those builds logs, I see:
>
> - failures in Test_popup_and_window_resize() on at least mips
> hppa, and sparc64
On Wed, Nov 01, 2017 at 09:22:45PM +0100, Bram Moolenaar wrote:
> That's defenitely better than an arbitrary delay. However, I think your
> check just never matches and causes a delay of one second.
That's surprising that WaitFor() silently fails, but you are right. I
tested this patch and it do
On Tue, Oct 31, 2017 at 10:20:14PM +0100, Bram Moolenaar wrote:
> *** ../vim-8.0.1240/src/testdir/test_popup.vim2017-10-27
> 01:34:55.093306847 +0200
> --- src/testdir/test_popup.vim2017-10-31 22:15:48.865608389 +0100
> ***
> *** 639,645
> endif
> let g:buf
I recently uploaded 8.0.1226 to Debian and nearly every build failed[0].
The most common failure is
Found errors in Test_popup_and_window_resize():
function RunTheTest[34]..Test_popup_and_window_resize line 16: Pattern
'^!\\s*$' does not match ''
function RunTheTest[34]..Test_popup_an
On Oct 19, 2017 14:03, "Tony Mechelynck"
wrote:
BTW I can't find any documentation about :[count]q in the Vim help (in
particular editing.txt, last change 2017 Aug 21; and version8.txt,
last change 2017 Apr 23). :[range]wq refers to the lines to be
written, which is obviously not what this thread
Consider the following two sets of commands.
1) vim -Nu NONE -c 'set fdc=2' -c 'normal! ggzf0zR'
Here, typing either "A" or "o" will create a new line that's not
part of the fold that the cursor started on.
2) vim -Nu NONE -c 'set fdc=2' -c 'put _' -c 'normal! ggzf0zR'
Here, typing "A" will creat
On Wed, Sep 27, 2017 at 03:04:00PM -0700, Gary Johnson wrote:
> On 2017-09-27, Bram Moolenaar wrote:
> > Dor Azouri wrote:
> >
> > > I would like to report a possible abuse one can perform on Vim's
> > > extensibility mechanism, that may lead to privilege escalation.
>
> > In my opinion, if a use
On Sun, Sep 17, 2017 at 09:00:19PM +0200, Bram Moolenaar wrote:
>
> Elimar Riesebieter wrote:
>
> > > > > > on a 32bit (i386) system I get:
> > > > > >
> > > > > > Found errors in Test_peek_and_get_char():
> > > > > > function RunTheTest[24]..Test_peek_and_get_char line 7: Expected 97
> > > >
On Sep 5, 2017 10:13, "Christian Brabandt" wrote:
On Di, 05 Sep 2017, Yegappan Lakshmanan wrote:
> From the documentation, it looks like NeoVim has the autocommands
> TermOpen and TermClosed which get triggered when a terminal buffer
> is opened or closed. In addition to your current change, sh
On Sep 1, 2017 11:22, "Taro MURAOKA" wrote:
Hi list and Bram.
When I try to access www.vim.org,
it returns 302 (redirect to) vim.sourceforge.io.
> $ curl -I http://www.vim.org
> HTTP/1.1 302 Found
> Server: nginx
> Date: Fri, 01 Sep 2017 15:16:22 GMT
> Content-Type: text/html; charset=iso-8859-
On Thu, Aug 31, 2017 at 10:36:34PM +0300, LCD 47 wrote:
> On 31 August 2017, Yegappan Lakshmanan wrote:
> > You can check for a particular patch [has("patch-8.0.1006")].
> [...]
>
> Yes, but that has its own set of problems, one of the main ones
> being that this kind of tests mean nothing wi
On Sat, Aug 19, 2017 at 07:41:09PM +0200, Bram Moolenaar wrote:
>
> Patch 8.0.0965
> Problem:The cursor shape is not reset after it was changed in a terminal.
> Solution: Request the original cursor shape and restore it. Add t_RS.
> Do not add t_SH for now, it does not work prop
On Aug 17, 2017 09:37, "François Ingelrest"
wrote:
Hi,
On 17 August 2017 at 14:24, James McCoy wrote:
> What exactly are the extra characters you're seeing? At a guess, it's
> something like "[2 q". If so, that's because libvte (until relatively
>
On Thu, Aug 17, 2017 at 09:00:13AM +0200, François Ingelrest wrote:
> Hi Bram,
>
> On 16 August 2017 at 21:09, Bram Moolenaar wrote:
> > I don't see this. Most likely related to using Gnome. Have you tried
> > using an xterm?
>
> I don't see this with an xterm or even in a console outside of X,
On Tue, Aug 15, 2017 at 09:38:09PM +0200, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > > > I see the following behaviour when running the terminal window (vim
> > > > 8.0.938):
> > > >
> > > > :term
> > > > :vim
> > > > (press ':')
> > > > libvterm: Unhandled control 0x9c
> > > >
On Mon, Aug 14, 2017 at 09:45:26PM +0200, Bram Moolenaar wrote:
> My experience is that term_wait() is not reliable. We basically wait
> for messages on the channel to be handled, but we never know if we got
> the messages we expected.
>
> It should be much more reliable (and faster) to wait for
I uploaded an updated Vim package to Debian with the terminal feature
enabled to get some broad test coverage[0] and feedback. We build 6
different variants of Vim, in shadowdirs, and then serially run the
tests for each variant.
[0]:
https://buildd.debian.org/status/logs.php?pkg=vim&ver=2%3A8.0
On Jul 31, 2017 11:16, "Tony Mechelynck"
wrote:
On Mon, Jul 31, 2017 at 4:29 PM, Ken Takata wrote:
> Hi Bram,
>
> Two years ago, you announced closing of Vim-multibyte mailing list.
>
> Vim-multibyte mailing list is closed
> https://groups.google.com/d/msg/vim_announce/3Kzdhtsp9dQ/afcHmpksN7QJ
>
On Sun, Jul 30, 2017 at 06:20:03PM +0200, Bram Moolenaar wrote:
>
> Patch 8.0.0817
> Problem:Cannot get the line of a terminal window at the cursor.
> Solution: Make the row argunt optionsl. (Yasuhiro Matsumoto, closes #1898)
Why wouldn't it use '.' to mean the current row? That would be
c
On Sat, Jul 29, 2017 at 03:14:29PM +0200, Bram Moolenaar wrote:
> I don't think this change is good when not running tests. We have the
> --not-a-term argument specifically for dealing with the situation that
> Vim is run without a terminal. How about doing this:
That does work. Thanks.
Cheers
Hi Bram,
Since Debian Stretch released, I've been catching up on Vim patches
however everything after 8.0.0314 was failing to build. The GUI-enabled
Vim builds were failing this part of Test_getcmdtype.
call feedkeys(":call input('Answer?')\", "t")
call feedkeys("MyCmd a\=Check_cmdline('@')\
ups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
POC.tar.gz
Description: application/gzip
commit f0b3e4fa57387068cbb2a82ad3931d8e1fb84d63
A
On Fri, Jul 07, 2017 at 11:54:43AM +0200, Bram Moolenaar wrote:
>
> Patch 8.0.0693
> Problem:No terminal emulator support. Cannot properly run commands in the
> GUI. Cannot run a job interactively with an ssh connection.
> Solution: Very early implementation of the :terminal co
On Mon, May 08, 2017 at 03:08:31PM -0500, R0b0t1 wrote:
> Or, *instead of all of the above,* arithmetic can be defined to wrap.
> Technically, with no other changes, this doesn't solve the original
> complaint about undefined behavior
It would, because it would be defined to wrap. That's trivial
On Fri, May 05, 2017 at 10:23:49PM +0200, Bram Moolenaar wrote:
> James McCoy wrote:
> > It would be nice for there to be defined behavior here for the user,
> > instead of exposing them to the whims of the compiler implementation.
>
> Unfortunately, that is quite diff
Hi all,
Recently, there was some work done on defining how to handle converting
numeric literals in vim script to C integers -- basically, clamp to the
extremes of the datatype. If it would exceed the max/min value, then
just treat it as the max/min value.
However, there's nothing defining how a
On Apr 21, 2017 10:25, "Manuel Ortega" wrote:
On Thursday, April 20, 2017 at 3:05:41 PM UTC-4, Manuel Ortega wrote:
> This patch unfortunately completely wrecks parallel builds on macOS
10.12.4.
As a side note, now that we know that the problem has nothing to do with
parallel builds but affects
On Mon, Mar 20, 2017 at 05:42:44PM -0700, Yegappan Lakshmanan wrote:
> On Mon, Mar 20, 2017 at 4:46 PM, James McCoy wrote:
> > Why keep shoe-horning things into the set{qf,loc}list functions? This
> > just makes it an awkward API to use.
> >
> > I wo
On Mon, Mar 20, 2017 at 08:26:27AM -0700, Yegappan Lakshmanan wrote:
> Hi all,
>
> When developing additional tests for the quickfix functionality,
> I found that some part of the code checks whether the quickfix
> or location list stack is empty. To test for these conditions, we
> need a function
On Mon, Mar 06, 2017 at 11:02:34PM +0100, Bram Moolenaar wrote:
>
> Michal Grochmal wrote:
>
> > I may be doing a horrible misinterpretation of the subject, but here goes
> > nothing.
> >
> > > > > > This just uses the existing logic in mch_can_exe to populate a
> > > > > > buffer with the
> >
1 - 100 din 343 matches
Mail list logo
