On Mon, Jul 4, 2022 at 11:48 AM Bram Moolenaar wrote:
>
>
> Patch 9.0.0033
> Problem:On a Belgian keyboard CTRL-[ does not work.
> Solution: Handle GDK_KEY_dead_circumflex. (Anton Sharonov, closes #10658)
> Files: src/gui_gtk_x11.c
FYI: In gvim 9.0.32 (Big, GTK3) i.e. without this
On Wed, Jun 22, 2022 at 2:52 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.5148
> Problem:Invalid memory access when using an expression on the command
> line.
> Solution: Make sure the position does not go negative.
> Files: src/ex_getln.c, src/testdir/test_cmdline.vim
With this patch,
On Sun, May 22, 2022 at 9:09 PM John Marriott wrote:
>
>
>
> On 23-May-2022 04:14, Bram Moolenaar wrote:
> > Patch 8.2.5003
> > Problem:Cannot do bitwise shifts.
> > Solution: Add the >> and << operators. (Yegappan Lakshmanan, closes #8457)
> > Files: runtime/doc/eval.txt,
On Sat, May 21, 2022 at 10:56 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.4995 (after 8.2.4992)
> Problem:Still a compiler warning for possibly uninitialized variable.
> (Tony Mechelynck)
> Solution: Initialize variables.
> Files: src/vim9execute.c
This
On Sat, May 21, 2022 at 7:57 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.4992 (after 8.2.4989)
> Problem:Compiler warning for possibly uninitialized variable. (Tony
> Mechelynck)
> Solution: Initialize variable in the caller instead of in the function.
> Files
Using gcc 12.1.0 on openSUSE Tumbleweed:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
-I/usr/include/harfbuzz -I/usr/include/freetype2
-I/usr/include/libmount -I/usr/include/blkid
On Sat, Apr 30, 2022 at 5:12 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.4850
> Problem:Mksession mixes up "tabpages" and "curdir" arguments.
> Solution: Correct logic for storing tabpage in session. (closes #10312)
> Files: src/session.c, src/testdir/test_mksession.vim
At this
On Tue, Apr 19, 2022 at 10:07 PM John Marriott
wrote:
>
> After this patch, mingw (gcc 11.2.0) throws this warning:
>
> gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603
> -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -D__USE_MINGW_ANSI_STDIO
> -pipe -march=native -Wall -O3
Warning "-Wmaybe-uninitialized" in all builds:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/ex_docmd.o ex_docmd.c
ex_docmd.c: In function ‘parse_command_modifiers’:
Here is my configuration for the failing build:
export CONF_OPT_GUI='--enable-gui=motif'
export CONF_OPT_FEAT='--with-features=small'
export CONF_ARGS2='--with-vim-name=vim-small'
export CONF_OPT_COMPBY='"--with-compiledby=antoine.mechely...@gmail.com"'
Best regards,
Tony
--
--
You received
IOW: does the Athena GUI (which I attempted to build) require support
of the NeXTaw GUI (which has been removed? Or is it "only" due to a
misplaced #ifdef?
I haven't (yet) tried to do a full rebuild by means of "make reconfig".
[...]
config.status: auto/config.h is unchanged
creating
I don't yet see the patch in the list but it has appeared on the
Mercurial server.
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/change.o change.c
change.c: In function
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/indent.o indent.c
I get the following in Small and Tiny at patchlevel 8.2.4014 (other
builds are OK):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce
-Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1 -o objects/option.o option.c
In file
On Sun, Jan 2, 2022 at 1:07 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > Using gvim 8.2.3978 (Big with GTK3) on openSUSE 5.3
> >
> > I would expect the +vim9script feature to be compiled-in (and be shown
> > as such) in all builds where has('vim9script') answers 1 even if, like
> >
Using gvim 8.2.3978 (Big with GTK3) on openSUSE 5.3
I would expect the +vim9script feature to be compiled-in (and be shown
as such) in all builds where has('vim9script') answers 1 even if, like
+vertsplit, +tag_binary, etc., it is present in all "modern" builds
from Tiny to Huge. But…
:echo
Only the Huge build succeeds but there are two different kinds of
failures in the other four:
1) In Small and Tiny:
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce
On Mon, Dec 20, 2021 at 11:14 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.3863 (after 8.2.3860)
> Problem:Various build flags accidentally enabled.
> Solution: Revert several lines in Makefile.
> Files: src/Makefile
>
After applying this patch, the "many warnings" went away. Thanks!
Best
On Mon, Dec 20, 2021 at 10:58 PM Tony Mechelynck
wrote:
>
> On Mon, Dec 20, 2021 at 10:36 PM Bram Moolenaar wrote:
> >
> >
> > > On Mon, Dec 20, 2021 at 5:43 PM tooth pik wrote:
> > > >
> > > > am i supposed to be getting (and ignoring?) a w
On Mon, Dec 20, 2021 at 10:36 PM Bram Moolenaar wrote:
>
>
> > On Mon, Dec 20, 2021 at 5:43 PM tooth pik wrote:
> > >
> > > am i supposed to be getting (and ignoring?) a warning on make
> > > that _FORIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
> > >
> >
> > I confirm that after
On Mon, Dec 20, 2021 at 5:43 PM tooth pik wrote:
>
> am i supposed to be getting (and ignoring?) a warning on make
> that _FORIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
>
I confirm that after applying patches 3857 to 3861, the compile step
for every single module in all five
Oops, there were more of those missing first-column T letters. Here is
a corrected version.
Best regards,
Tony.
On Tue, Nov 30, 2021 at 12:08 AM Tony Mechelynck
wrote:
>
> I'm attaching a proposed patch. I suppose it may be included the next
> time a runtime files update comes around.
the web visit
https://groups.google.com/d/msgid/vim_dev/CAJkCKXvLiQkAHfs77ukR6W4dP7DF2BBLATju9dGo3FKimjFQxw%40mail.gmail.com.
# HG changeset patch
# User Tony Mechelynck
# Parent 17cb818735c87b74488c9ce6054d03405b1214f7
graduate +title in the list under +feature-list
diff --git a/runtime/doc/vario
No error in Tiny with no GUI and no error in Normal to Huge with GTK3
GUI. This build is configured by sourcing the following commands in
the same bash shell:
export CONF_OPT_GUI='--enable-gui=motif'
export CONF_OPT_FEAT='--with-features=small'
export CONF_ARGS2='--with-vim-name=vim-small'
export
On Mon, Nov 8, 2021 at 7:46 PM 'hebar...@googlemail.com' via vim_dev
wrote:
>
> After adding a line with "o" (on an indented line with "autoindent" on) then
> (while being in INSERT mode) using "^O" to enter a NORMAL mode command the
> cursor jumps back to the beginning of the line (erasing the
Thanks for this changeset:
| |
| o changeset: 27210:00de6cb1c5a1
| | parent: 27208:19640c9a9e18
| | user:Bram Moolenaar
| | date:Wed Nov 03 23:30:04 2021 +0100
| | files: src/version.c
| | description:
| | Add missing piece of patch 8.2.3578
| |
| | Commit:
On Wed, Nov 3, 2021 at 10:57 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.3578
> Problem:Manipulating highlighting is complicated.
> Solution: Add the hlget() and hlset() functions. (Yegappan Lakshmanan,
> closes #9039)
> Files: runtime/doc/eval.txt, runtime/doc/syntax.txt,
>
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce
-Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/optionstr.o optionstr.c
In file included from optionstr.c:14:0:
optionstr.c: In function ‘did_set_string_option’:
On Sun, Oct 17, 2021 at 1:33 AM Dusan Popovic wrote:
>
> On 17/10/21, Tony Mechelynck wrote:
> > gui_gtk_x11.c:5749:13: warning: ‘should_need_pango’ may be used
>
> I just read code again and I don't see any path to reach assignment that
> happens later on before varia
In GTK builds (here GTK3):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/gtk-3.0
-I/usr/include/gio-unix-2.0
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/ex_cmds.o ex_cmds.c
ex_cmds.c: In function ‘ex_substitute’:
ex_cmds.c:3727:25: warning: implicit declaration of function
On Sun, Aug 8, 2021 at 7:57 PM Bram Moolenaar wrote:
> Tony wrote: [...]
>
> Hmm, I don't really want to allow using :scriptversion at the command
> line, it is really meant to be used in a script.
>
> We should be able to use the ":vim9cmd" modifier. However, it appears
> not to work. I can
Example:
:scriptversion 4 | echo 123'456'789 | scriptversion 1 | echo 123'456'789
now gives
E984: :scriptversion used outside of a sourced file
I suggest displaying
123456789
123 456 789
instead.
This would make it possible to use at the command-line syntaxes not
link.sh: $LINK_AS_NEEDED set to 'yes': invoking linker directly.
gcc -L/usr/local/lib -Wl,--as-needed-o vi objects/arabic.o
objects/arglist.o objects/autocmd.o objects/beval.o objects/buffer.o
objects/change.o objects/blob.o objects/blowfish.o objects/cindent.o
objects/clientserver.o
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/gtk-3.0
-I/usr/include/gio-unix-2.0 -I/usr/include/libxkbcommon
-I/usr/include/wayland
On Thu, Jul 22, 2021 at 7:11 AM Martin Tournoij
wrote:
>
> These are "raw" dumps of emails, and pretty much everyone uses and
> expects DOS line endings, as specified in RFC5322.
Warning: 'fileformats' (plural) is a global (only) setting. This means
that changing it, even with :setlocal, will
On Tue, Jul 20, 2021 at 9:08 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.3190
> Problem:Error messages are spread out.
> Solution: Move error messages to errors.h and give them a clear name.
> Files: src/globals.h, src/errors.h, src/buffer.c, src/debugger.c,
> src/digraph.c,
The following is for Normal vim. "Bigger" builds have the same
warning, just a longer gcc command-line. The "make" step contiues and
links an executable.
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0
-I/usr/include/at-spi-2.0
On Fri, May 28, 2021 at 12:55 AM justrajdeep wrote:
>
> Hi
>
> I have a file and a soft link to it
>
>
> ls -ltr $OUT/src/verif/gl2cc/gl2cc_top/tb/gl2cc_top_tb_pkg.sv
> lrwxrwxrwx 1 ramondal gfx11 85 May 27 10:21
> $OUT/src/verif/gl2cc/gl2cc_top/tb/gl2cc_top_tb_pkg.sv ->
>
On Sat, Apr 24, 2021 at 7:08 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.2806
> Problem:Vim9: using "++nr" as a command might not work.
> Solution: Do not recognize "++" and "--" in a following line as addition or
> subtraction.
> Files: src/vim9compile.c, src/ex_docmd.c,
吕海涛 : When looking for information about Vim, the place to look is
always the built-in help. Not Google, not the manpages, not the github
metadata, just the help. In this case: :help credits
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
My vimrc includes the following snippet:
if has('unix')
language messages C
else
language messages en
endif
I just noticed that repeatedly hitting % (with matchit enabled) cycles
from the if to the else to the en in "language messages en" and back.
% on the final endif goes to the next outer
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-o objects/ex_getln.o ex_getln.c
ex_getln.c:
After applying 8.2 patches 2680-2681, I get he following errors in
Tiny and Small:
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations
For some reason tag v8.2.2677 was not set, at least on the Mercurial
mirror http://hg.256bit.org/vim (I haven't checked the git master).
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
As far as I can remember, the Vim groups have always used polite language
and understanding behaviour. You can't legislate that, but you can
encourage it by example. Some of the points of that so-called code of
conduct, for instance making so-called inclusive language mandatory in all
On Fri, Feb 19, 2021 at 5:36 AM Haodong Du wrote:
> Thank you Gary. Your explanation is very clear. Indeed with TERM=screen*
> the query returns nothing.
> But I'm still a little confused as it seems Vim can detect background from
> screen with the same TERM as tmux. But not always, in some
On Thu, Feb 18, 2021 at 8:15 PM Tim Lee wrote:
>
> Where should I submit patches for runtime files? Is it to the runtime
> file's maintainer, or can I make a pull request to Vim on GitHub?
>
> According to the contributing instructions for runtime files
>
On Fri, Feb 12, 2021 at 10:09 PM Pavel Tavoda wrote:
>
> Maybe it was discussed before but it will be very helpful to get IDE like
> experience with VIM if we can have more buffers in one window and they will
> be visible like small 'subtabs' on window border.
> I know that VIM is not IDE but
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/gtk-3.0
-I/usr/include/gio-unix-2.0 -I/usr/include/libxkbcommon
-I/usr/include/wayland
On Wed, Jan 20, 2021 at 4:20 PM Ernie Rael wrote:
>
> Hi all,
>
> jVi had a feature request, something about supporting
>
> let @a= "some string"
>
> which is supposed to initialized the named buffer at startup. Something
> the user wanted to use with macros. I pointed out that jVi persists
>
The various.txt helpfile (Last change 2020 Nov 16) says at line 414
that +multi_byte is enabled on Normal and bigger builds. However my
Tiny and Small builds, which I configure without specifying whether to
enable or disable that feature, display +multi_byte as part of their
--version output.
I
The warning happens in all builds except Tiny and Small, as seen
below. I believe that this warning is spurious because just above it
there is (omitting irrelevant code)
if (name != NULL)
{
if (error != FCERR_NONE)
res = FAIL;
else
res = call_by_name(fname,
Oops - I don't have Syntastic; but have you tried a more recent
version? The latest version as of this writing is 8.2.2306 and the
8.2.0 release happened on 12 December 2019, more than a year ago.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
On Wed, Jan 6, 2021 at 5:14 PM Philip Pemberton wrote:
>
> I recently installed Syntastic (https://github.com/vim-syntastic/syntastic/)
> under Vim 8.1 (from https://launchpad.net/~jonathonf/+archive/ubuntu/vim ) on
> Ubuntu 18.04, and have stumbled upon an odd issue.
>
> If I start gvim
On Sun, Jan 3, 2021 at 10:13 PM Bram Moolenaar wrote:
>
> Thanks for reporting. I don't think we have a CI test with Motif.
>
Well, at the moment I build the following:
- Huge with several interpreted languages and GTK3 GUI
- Big and Normal with GTK3 GUI
- Small with Motif GUI
- Tiny with no GUI
On Sun, Jan 3, 2021 at 7:52 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.2289
> Problem:Vim9: 'cpo' can become empty.
> Solution: Use empty_option instead of an empty string. Update quickfix
> buffer after restoring 'cpo'. (closes #7608)
> Files: src/evalfunc.c, src/syntax.c,
On Sat, Jan 2, 2021 at 2:03 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > gvim 8.2.2267 (Big) with GTK3 GUI; 'encoding' = utf-8; 'filencodings'
> > (plural) = ucs-bom,utf-8,latin1
> >
> > Steps to reproduce:
> > 1. Load a Latin1 file containing only characters in the range
> > 0x00-0x7F. (In
gvim 8.2.2267 (Big) with GTK3 GUI; 'encoding' = utf-8; 'filencodings'
(plural) = ucs-bom,utf-8,latin1
Steps to reproduce:
1. Load a Latin1 file containing only characters in the range
0x00-0x7F. (In my case this was a corrupt version of the file.)
-- 'fileencoding' is set to utf-8, which at this
Like Yegappan said, many contributors are mentioned under ":help
credits". Christian and Yegappan are there at the very bottom (they
are "last but not least") and I am there too, though I didn't
specifically ask for it AFAIR, and I feel flattered, though as far as
I'm concerned, "by Bram Moolenaar
On Sun, Dec 27, 2020 at 4:55 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.2228
> Problem:Vim9: cannot use ":e #" because # starts a comment.
> Solution: Support using %% instead of #.
> Files: src/ex_docmd.c, src/testdir/test_vim9_cmd.vim
I get the following compile warning and link error
Fatal eror compiling ex_docmd.c with Tiny or Small features:
linux-2iyu:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
[...]
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o
After all, since the patch is available on the repos, I thought I
could just as well send it to where it's missing. Here's the metadata:
user:Bram Moolenaar
date:Fri Nov 27 21:00:04 2020 +0100
files: src/terminal.c src/testdir/test_termcodes.vim src/version.c
description:
Patch 8.2.2061 "Vim9: E1030 error when using empty string for
term_sendkeys()" has been published (git CSID 4d05af0a64c2, Mercurial
CSID bc3a083b50cb) but I don't see it on the vim_dev list.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
On Sun, Nov 15, 2020 at 8:33 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.1990
> Problem:Cursor position wrong in terminal popup with finished job.
> Solution: Only add the top and left offset when not done already.
> (closes #7298)
> Files: src/popupwin.c, src/structs.h,
:version output begins as follows:
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Nov 5 2020 21:36:19)
Included patches: 1-1959, 1959-1961
Compiled by antoine.mechely...@gmail.com
Big version with GTK3 GUI. Features included (+) or not (-):
- AFAIK this is harmless.
- I pull my sources from the
: in function `ins_complete':
insexpand.c:(.text+0x4abd): undefined reference to
`ins_compl_update_sequence_numbers'
collect2: error: ld returned 1 exit status
link.sh: Linking failed
make: *** [Makefile:2134: vi] Error 1
exit status 2
On Mon, Oct 26, 2020 at 11:12 PM Tony Mechelynck
wrote:
>
> W
Warning mesage as follows at patchlevel 8.2.1910 in Tiny and Small
builds only. Link proceeds to completion.
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/insexpand.o
insexpand.c
insexpand.c: In function
Second paragraph of the g_CTRL-G help.
There is:
If there are characters in the line that take more
than one position on the screen ( or special
character), both the "real" column and the screen
column are shown, separated with a dash.
I suggest:
After patch 8.2.1881 the problems from 1875 and 1878 are solved
AFAICT: Vim with GTK3 builds again.
Best regards,
Tony.
--
--
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
:50 CEST 2020
Best regards,
Tony.
On Wed, Oct 21, 2020 at 4:11 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.1878
> Problem:GTK: error for redefining function. (Tony Mechelynck)
> Solution: Remove "gtk_" prefix from local functions and prepend "gui_" to
>
P.S. "make reconfig" does not clear the problem. My GTK3 version is
3.24.20 and my compiler is gcc 7.5.0.
On Wed, Oct 21, 2020 at 2:53 PM Tony Mechelynck
wrote:
>
> On Wed, Oct 21, 2020 at 12:38 PM Bram Moolenaar wrote:
> >
> >
> > Patch 8.2.1875
> > P
On Wed, Oct 21, 2020 at 12:38 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.1875
> Problem:Warning when building GTK gui.
> Solution: Add missing function parameter.
> Files: src/gui_gtk_f.c
Fatal error in gui_gtk_f.c after applying patches 8.2.1874 to 1876
(not yet 1877):
gcc -c -I.
On Mon, Sep 28, 2020 at 11:23 PM Ben Jackson
wrote:
> Does it happen also in gvim?
>
> Will check motif GUI at work tomorrow, sorry don't have a gvim here right
> now.
>
> For the record, it *does* repro in MacVim with:
>
> ben@BenMBP vim-clean % gvim --version
> VIM - Vi IMproved 8.2 (2019 Dec
I don't know the state of the git repository, but on the Mercurial
repository, patch 8.2.1700 (Mercurial changeset 36e8e046c335) has no
tag.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
On Fri, Aug 14, 2020 at 1:36 PM John Sellers wrote:
>
> This is happening on my new month year old computer as well as my 10+ year
> old computer.
>
> The behavior is exactly the same on both computers when using Gvim to open a
> .txt file. (I have not checked other kinds of files).
>
> While
On Tue, Aug 4, 2020 at 8:01 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > According to ":h +builtin_terms", there are no builtin terminals in
> > Tiny or Small (I think this is a documentation error), some in Normal,
> > and all in Big and Huge. The following, however, is what ":set
> >
According to ":h +builtin_terms", there are no builtin terminals in
Tiny or Small (I think this is a documentation error), some in Normal,
and all in Big and Huge. The following, however, is what ":set
term=xxx" gives me in Console mode in each build:
Tiny with no GUI:
builtin_ansi
On Thu, Jul 30, 2020 at 11:12 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.1328
> Problem:No space allowed before comma in list.
> Solution: Legacy Vim script allows it. (closes #6577)
> Files: src/dict.c, src/list.c, src/testdir/test_listdict.vim
Sure, legacy Vim script allows it; but
On Mon, Jul 27, 2020 at 4:03 PM Ali wrote:
>
> Is it? I wasn't exactly sure so I posted here in case there was some
> resolution.
Use whatever package manager your system provides to check that the
following are installed:
• the ncurses library;
• the ncurses development package (on my system
Hadn't seen that the [^(] was added after the \>. That's clever.
The next line starts with a space followed by a tab. My patch took
care of that but I should have mentioned it more explicitly.
Line-continuation betwen "function" and the function name makes % not
work — the marginal case I
On Sun, Jul 26, 2020 at 4:42 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > Not sure how easy this will be to fix; I just noticed it. Also not
> > sure of whether the problem is in matchit.vim, in
> > $VIMRUNTIME/ftplugin/vim.vim, or in both.
> >
> > Software in use:
> > Vim or gvim, Big
b visit
https://groups.google.com/d/msgid/vim_dev/CAJkCKXvpJJmWDWfhaQ7cTVHO8v642Z5YLpLLruxoJws004UToQ%40mail.gmail.com.
# HG changeset patch
# User Tony Mechelynck
# Parent 5d927b1aca7c85b6fe30a9077046e681445e4025
Avoid confusing function( with the start of a function definition when using matchit on Vim script
diff --git a/r
On Sun, Jul 19, 2020 at 10:10 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > On Sun, Jul 19, 2020 at 7:48 PM Bram Moolenaar wrote:
> > >
> > >
> > > Patch 8.2.1250
> > > Problem:Vim9: cannot use the g:, b:, t: and w: namespaces.
> > > Solution: Add instructions to push a dict for the
On Sun, Jul 19, 2020 at 7:48 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.1250
> Problem:Vim9: cannot use the g:, b:, t: and w: namespaces.
> Solution: Add instructions to push a dict for the namespaces. (closes #6480)
> Files: src/vim9.h, src/vim9compile.c, src/vim9execute.c,
>
Example:
:dig += 0x2A72
E39: Number expected
:dig += 10866
(no error)
:echo 0x2A72 == 10866
1
Now that Unicode codepoints are usually given in hex (in this case,
U+2A72 PLUS SIGN ABOVE EQUALS SIGN, as used in chess to mean "slight
advantage for White") it would
On Sat, Jul 11, 2020 at 8:27 PM Yegappan Lakshmanan wrote:
>fourchette (hippologie)
> Hi,
>
> On Sat, Jul 11, 2020 at 11:21 AM Kuriyama Kazunobu
> wrote:
>>
>> My understanding is that macOS is a certified Unix and that every Unix user
>> expects that X Windowing System runs there. For that,
Ah, this ought to be fixed by patch 1180 Let's see.
Best regards,
Tony.
--
--
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 this message
After applying patches 1177 and 1178 (to Vim 8.2) I get the following
compile warning and link error in non-eval builds:
linux-2iyu:~/.build/vim/vim-hg/src/shadow-small # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MOTIF -O2
On Fri, Jul 10, 2020 at 5:00 PM Yegappan Lakshmanan wrote:
>
> Hi Tony,
>
> On Fri, Jul 10, 2020 at 7:37 AM Tony Mechelynck
> wrote:
>>
>> On Fri, Jul 10, 2020 at 3:41 AM Yegappan Lakshmanan
>> wrote:
>> >
>> > Hi all,
>> >
On Fri, Jul 10, 2020 at 3:41 AM Yegappan Lakshmanan wrote:
>
> Hi all,
>
> Is anyone able to successfully build GUI Vim on MacOS?
>
> I am not able to build Vim with GUI enabled on MacOS. I tried athena and
> carbon.
> I think the build instructions in src/INSTALLmac.txt file should be updated.
On Thu, Jul 2, 2020 at 11:25 AM Christian Brabandt wrote:
>
>
> On Di, 20 Aug 2019, Tony Mechelynck wrote:
>
> > Full details:
> > https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
> >
> > TLDR: Bit bucket won't allow creating *new* Mer
cduOn Tue, Jun 30, 2020 at 11:35 PM Yegappan Lakshmanan
wrote:
>
> Hi,
>
> I came across the following Vim wish list (maintained by Sven Guckes who used
> to regularly contribute to the vim list in those days) from two decades ago.
>
>
On Wed, Jun 10, 2020 at 10:18 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.0956 (after 8.2.0953)
> Problem:Spell test fails.
> Solution: Add missing change the spell checking.
> Files: src/spell.c
This gives me a warning -Wmaybe-uninitialized in all +eval builds, as follows:
gcc -c -I.
On Tue, Jun 9, 2020 at 2:50 PM Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > 2020/6/9 Tue 1:55:38 UTC+9 Bram Moolenaar wrote:
> > >
> > >
> > > Patch 8.2.0932
> > > Problem:Missspelling spelllang.
> > >
> >
> > Oh, you misspelled the word misspelling.
>
> Should be Missspellling ? :-)
On Sat, Jun 6, 2020 at 4:18 PM Matt wrote:
>
> Thanks for the detailed explanation, I would like to combine 6
> characters to create one multibyte code as you mentioned here:
>
> >But this is not all. Unicode also knows combining characters, which occupy
> >no space by themselves but are printed
Well, originally Unicode codepoints were foreseen as possibly someday
extending from U+ to U+7FFF; UTF-32 (aka UCS-4) and UTF-8 can
address that, and Vim too; but UCS-2 could only address the BMP (the Basic
Multilingual Plane), i.e. up to U+. Later UCS-2 was expanded to UTF-16
by means
On Fri, Jun 5, 2020 at 11:17 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.0910
> Problem:Vim is not reproducibly buildable.
> Solution: Use the $SOURCE_DATE_EPOCH environment variable in configure.
> (James McCoy, closes #513) Give a warning about using it.
Does this mean that
My "Tiny" build, configured with -gui -xim, nevertheless compiles and
links objects/gui_xim.o — is this intended? (It neither compiles nor
links any other gui_* module.)
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
On Wed, May 27, 2020 at 9:30 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > Bram, did the message below fall off your radar? AFAICT the warning
> > (in +eval builds) is still extant.
>
> I indeed didn't spot it. I only see it when compiling with -O2, and the
> get tons of errors in library
101 - 200 din 2203 matches
Mail list logo
