Re: [SOLVED] Re: Commit: patch 9.1.0297: Patch 9.1.0296 causes too many issues

On Thu, Apr 11, 2024 at 3:21 AM Tony Mechelynck wrote: > > On Wed, Apr 10, 2024 at 4:30 PM Christian Brabandt wrote: > > > > patch 9.1.0297: Patch 9.1.0296 causes too many issues > > > > Commit: > > https://github.com/vim/vim/commit/c97f4d61cde24030f2f7d2318e

[SOLVED] Re: Commit: patch 9.1.0297: Patch 9.1.0296 causes too many issues

4 +0200 > > patch 9.1.0297: Patch 9.1.0296 causes too many issues > > Problem: Patch 9.1.0296 causes too many issues > (Tony Mechelynck, @chdiza, CI) > Solution: Back out the change for now […] After this patch, the many errors I got when opening CSS (o

CSS syntax suddenly produces lots of errors

Suddenly when opening a CSS file in Vim (or when opening an HTML file, because HTML syntax invokes CSS syntax), I see a huge lot of errors. This is at patchlevel 9.1.296 or earlier. I didn't see it a few days ago but I'm not sure at which changeset it appeared. I'm copying below what I saw while

Patchlevel 283 mistakenly tagged v9.1.0282 on Mercurial

Patchlevel 283 (csid 67dc61280eba) was mistakenly tagged v9.1.0282 on Mercurial, depriving changeset 3d1e6800e2a8 of its legitimate tag. I don't know which tags, if any, are set on the git repository. Patch numbers in src/version.c are OK. Best regards, Tony. -- -- You received this message

Compile warning in insexpand.c with +eval after applying patches 9.1.189-190

For instance in Normal build : In function ‘get_complete_info’, inlined from ‘f_complete_info’ at insexpand.c:3175:5: insexpand.c:3123:31: warning: ‘li’ may be used uninitialized [-Wmaybe-uninitialized] 3123 | ret = list_append_dict(li, di); |

Re: Commit: runtime(mswin): revert back the check for clipboard_working support

On Wed, Mar 13, 2024 at 4:45 PM Christian Brabandt wrote: > > runtime(mswin): revert back the check for clipboard_working support > > Commit: > https://github.com/vim/vim/commit/760f664213dea9a300454992ba1589f4601d622f > Author: Christian Brabandt > Date: Wed Mar 13 16:38:16 2024 +0100 […]

and composing characters in Insert mode with 'delcombine' on : Bug or feature ?

In Insert mode with 'delcombine' set, when the cursor is in a screen cell containing not only a spacing character but also one or more combining characters (or, in gvim, seems to be between that screen cell and the one before it) skips the spacing character and removes a composing character (I

Re: Proposal/Discussion on decoupling clipboard functionality from X11

On Sat, Feb 10, 2024 at 1:15 AM Luca Saccarola wrote: > > > Ok, so option two for a possible solution is not really an option. > Thanks for letting me know. > > But in your reply you aren't even acknowledge the first possible > solution witch I think solve a legitimate problem in vim's usability,

Re: Proposal/Discussion on decoupling clipboard functionality from X11

On Fri, Feb 9, 2024 at 8:20 PM 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 > === > > Currently in vim,

[FIXED]: gcc still complains about use of uninitialized var

1 22:10:50 2024 +0100 > > patch 9.1.0067: gcc still complains about use of uninitialized var > > Problem: gcc still complains about use of uninitialized var > ((Tony Mechelynck, after 9.1.0064/9.1.0066)) > Solution: This time init the correct variable &g

Re: Commit: patch 9.1.0066: gcc complains about use of uninitialized var

4 +0100 > > patch 9.1.0066: gcc complains about use of uninitialized var > > Problem: gcc complains about use of uninitialized var > (Tony Mechelynck, after 9.1.0064) > Solution: initialize button to silence gcc > > Signed-off-by: Christian B

Warning in gui_gtk_x11.c at changeset hg:d15d40bf532b — git:8fecb472c4a3f0f1ea364422424c56d1e0771b3e

gui_gtk_x11.c: In function ‘scroll_event’: gui_gtk_x11.c:2135:9: warning: ‘button’ may be used uninitialized [-Wmaybe-uninitialized] 2135 | gui_send_mouse_event(button, (int)event->x, (int)event->y, | ^~ 2136 |

Re: "around word" doesn't behave consistently due to white space, why?

On Fri, Jan 19, 2024 at 5:50 PM Gary Johnson wrote: > > 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) > > > >

Wrong Mercurial tag and description patchno

The following is in error: | o changeset: 36588:730a3ddebdd2 | | tag: v9.0.2175 | | user:Christian Brabandt | | date:Tue Dec 19 20:15:06 2023 +0100 | | files: src/optionstr.c src/version.c | | description: | | patch 9.0.2175: Compile error with Motif UI +

Re: Mercurial "Connection refused" for "hg in" on http://hg.256bit.org/vim

On Mon, Dec 18, 2023 at 9:23 AM Christian Brabandt wrote: > > > On So, 17 Dez 2023, Tony Mechelynck wrote: > > > linux-tuxedo:~/.build/vim/vim-hg # hg paths > > bitbucket = https://bitbucket.org/vim-mirror/vim > > default = http://hg.256bit.org/vim > > osd

Re: After applying patches 9.0.2168 to 9.0.2173 : warning -Wmaybe-uninitialized in vim9cmds.c (not in Tiny)

On Sun, Dec 17, 2023 at 3:26 AM Yegappan Lakshmanan wrote: > > Hi Tony, > > On Sat, Dec 16, 2023 at 3:50 PM Tony Mechelynck > wrote: >> >> vim9cmds.c: In function ‘compile_defer’: >> vim9cmds.c:2051:18: warning: ‘type’ may be used uninitialized >> [-Wmaybe

After applying patches 9.0.2168 to 9.0.2173 : warning -Wmaybe-uninitialized in vim9cmds.c (not in Tiny)

vim9cmds.c: In function ‘compile_defer’: vim9cmds.c:2051:18: warning: ‘type’ may be used uninitialized [-Wmaybe-uninitialized] 2051 | else if (check_func_args_from_type(cctx, type, argcount, TRUE, | ^ 2052 |

Re: Missing tags (again) on Mercurial

On Tue, Dec 12, 2023 at 8:41 AM Christian Brabandt wrote: > > > On Di, 12 Dez 2023, Tony Mechelynck wrote: > > > Something has gone wrong again. > > > > Remember: tags v9.0.2140 to v9.0.2142 had gone missing, but tags > > v9.0.2143 to v9.0.2155 had been set cor

Missing tags (again) on Mercurial

Something has gone wrong again. Remember: tags v9.0.2140 to v9.0.2142 had gone missing, but tags v9.0.2143 to v9.0.2155 had been set correctly. Well, now tags v9.0.2156 to v9.0.2158 have gone missing again. This concerns only the Mercurial .hgtags metadata (and I don't know about any git

Missing tags in the latest batch of Mercurial changesets

I added the following to my Mercurial clone of the Vim distribution. The changeset ID at the top of each new changeset may be different from those you will get if and when you add them: @ changeset: 36508:24a1f9015465 | tag: tip | user:Tony Mechelynck | date:Sun Dec

Re: Problem in vim-enahanced rpm for ALMALINUX8 causing segmentation fault.

On Wed, Nov 15, 2023 at 6:55 PM Tony Mechelynck wrote: > > On Tue, Oct 31, 2023 at 1:53 PM varun bali wrote: > > > > Hi, > > > > We are facing segmentation fault in vim-enhanced rpm, when we are opening > > two or more files simultaneously from v

Re: Problem in vim-enahanced rpm for ALMALINUX8 causing segmentation fault.

On Tue, Oct 31, 2023 at 1:53 PM varun bali wrote: > > Hi, > > We are facing segmentation fault in vim-enhanced rpm, when we are opening two > or more files simultaneously from vim on same server, then if we reboot the > system vim generates core/crashes. Attaching gdb log for same and core file

Build failure in vim9class.c in +eval builds after updating source to 9.0.2086

For example in Normal build: In file included from vim.h:570, from vim9class.c:15: vim9class.c: In function ‘ex_class’: vim9class.c:1563:24: error: ‘e_abstract_must_be_followed_by_def_or_static’ undeclared (first use in this function); did you mean

Re: Commit: patch 9.0.2050: Vim9: crash with deferred function call and exception

On Thu, Oct 19, 2023 at 11:00 AM Christian Brabandt wrote: > > patch 9.0.2050: Vim9: crash with deferred function call and exception [...] This patch lacks a change to src/version.c so when running the executable, :intro and :version both say it is patchlevel 2049. The repository tags are OK

Re: [vim/vim] vim.org should redirect to www.vim.org (Issue #11259)

On Sun, Oct 2, 2022 at 7:52 PM Martin Tournoij wrote: > This has been mentioned several times, but the maintainer of the DNS > records says it doesn't work. I forgot the details. > Fortunately several browsers handle this if you type "vim.org". > > Neither Firefox not Chromium on my system do

Compile warning -Wmaybe-uninitialized about xxd (in gcc 13.2.1) for all featuresets of Vim

cd xxd; CC="gcc" CFLAGS=" -O2 -fno-strength-reduce -Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1" LDFLAGS="-L/usr/local/lib -Wl,--as-needed" \ make -f Makefile make[1]: Entering directory '/root/.build/vim/vim-hg/src/shadow-tiny/xxd' gcc -O2

Re: Warning message -Wunused-function at optionstr.c:901 in Normal and Tiny after applying patches up to 9.0.1989

Oops... to 9.0.1991. On Thu, Oct 5, 2023 at 9:16 PM Tony Mechelynck wrote: > > 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

Warning message -Wunused-function at optionstr.c:901 in Normal and Tiny after applying patches up to 9.0.1989

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 optionstr.c:902:1: warning: ‘expand_set_opt_callback’ defined but not used [-Wunused-function]

Re: Moving the Vim Homepage on 26.09.2023

P.S. I also tried with Firefox instead of SeaMonkey, with the same (lack of) results. 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

Re: Moving the Vim Homepage on 26.09.2023

g, please let me know and I'll fix it. > > Best, > Christian > -- > The fancy is indeed no other than a mode of memory emancipated from the order > of space and time. -- Samuel Taylor Coleridge > This is Tony Mechelynck and I'm using the mail interface because the Google G

Re: Updates on the Vim project

On Mon, Aug 28, 2023 at 9:11 PM Christian Brabandt wrote: > > > On Mo, 28 Aug 2023, Tony Mechelynck wrote: > > > Christian, do you have any recommendations for someone who would want > > to continue porting the changes from git to Mercurial if you ever > > deci

Re: Updates on the Vim project

On Mon, Aug 28, 2023 at 7:05 PM Christian Brabandt wrote: […] > I use git, because all the information can easily be found in the > internet and it is still very actively developed and a lot of questions > on how to use it have already been asked :). > > For mercurial I have to refresh my

Re: Updates on the Vim project

On Thu, Aug 24, 2023 at 4:17 PM Ernie Rael wrote: > > On 23/08/24 2:44 AM, Tony Mechelynck wrote: > > [...] > > Well, if the Mercurial mirror goes puff, I'll have to decide > > either to fall back on the Vim from my distro (always somewhat behind, > > currentl

Re: Updates on the Vim project

On Wed, Aug 23, 2023 at 10:18 PM Christian Brabandt wrote: [...] > For a similar reason and because of the mess I created with the > mercurial mirror, I am thinking to retire the mercurial repository. I > think it is pretty clear that nowadays git is the preferred VCS of > choice for most

Re: Commit: patch 9.0.1786: Vim9: need instanceof() function

On Thu, Aug 24, 2023 at 8:01 AM Christian Brabandt wrote: > > > On Do, 24 Aug 2023, Christian Brabandt wrote: > > > > > On Mi, 23 Aug 2023, Tony Mechelynck wrote: > > > > > Discontinuous tagging again : notice the second line below. > > > > >

Re: Commit: patch 9.0.1786: Vim9: need instanceof() function

On Wed, Aug 23, 2023 at 9:15 PM Christian Brabandt wrote: > > patch 9.0.1786: Vim9: need instanceof() function > > Commit: > https://github.com/vim/vim/commit/afe0466fb1695fa8b9782eea8a8e9f9540d4cb85 > Author: LemonBoy > Date: Wed Aug 23 21:08:11 2023 +0200 [...] Discontinuous tagging again

Re: Patch 9.0.1678

15 hours after Christian's message, the runtime/filetype.vim at https://github.com/vim/vim/tree/master/runtime still seems not to have been updated since patchlevel 9.0.1668 — and of course patch 1678 hasn't yet appeared on the Mercurial repository either, because it gets its updates from the git

Re: :tearoff command not available in Vim 9.0.1664 for Linux even when exists(':tearoff') == 2

On Mon, Jun 26, 2023 at 1:31 PM Bram Moolenaar wrote: > > > Tony wrote: > > > • In Normal gvim with Motif GUI in GUI mode, :echo exists(':tearoff') > > gives 0 but menus can be teared off from the menu bar with the mouse > > • In the same in Console mode, :echo exists(':tearoff') gives 2 > > • In

Re: After recent "Normalize line endings" changeset (448aef880252 Mercurial-only AFAICT) Make says file missing

On Mon, Jun 26, 2023 at 1:14 PM Christian Brabandt wrote: > > > On Mo, 26 Jun 2023, Tony Mechelynck wrote: > > > On Mon, Jun 26, 2023 at 12:10 PM Christian Brabandt wrote: > > > > > > > > > On Mo, 26 Jun 2023, Tony Mechelynck wrote: > > >

Re: After recent "Normalize line endings" changeset (448aef880252 Mercurial-only AFAICT) Make says file missing

On Mon, Jun 26, 2023 at 12:10 PM Christian Brabandt wrote: > > > On Mo, 26 Jun 2023, Tony Mechelynck wrote: > > > At hg CSID 448aef880252 by Christian Brabandt: Problem detected at or > > near src/Makefile line 1972. I believe there is a problem of some kind > >

After recent "Normalize line endings" changeset (448aef880252 Mercurial-only AFAICT) Make says file missing

At hg CSID 448aef880252 by Christian Brabandt: Problem detected at or near src/Makefile line 1972. I believe there is a problem of some kind with src/auto/config.mk or src/shadow/auto/config.mk. Neither plain "make" nor "make reconfig" work. For the time being I have updated back to previous

:tearoff command not available in Vim 9.0.1664 for Linux even when exists(':tearoff') == 2

• In Normal gvim with Motif GUI in GUI mode, :echo exists(':tearoff') gives 0 but menus can be teared off from the menu bar with the mouse • In the same in Console mode, :echo exists(':tearoff') gives 2 • In Huge gvim with GTK3 GUI (where menus cannot be teared off with the mouse), :echo

Re: Patch 9.0.1638

On Sat, Jun 17, 2023 at 4:01 PM Bram Moolenaar wrote: > > > Patch 9.0.1638 (after 9.0.1637) > Problem:crypt tests hang and cause memory errors > Solution: Move variable to start of function. > Files: src/fileio.c [...] This gives me a compiler warning in the Tiny build, as follows:

Re: X11 requirements -- solved

On Thu, Jun 15, 2023 at 5:24 PM tooth pik wrote: > > i thought i had exhausted google, but with yet another stab at it, in > vim.fandom.com i found reference to two packages i didn't have: libxpm-dev > and libxt-dev > > i added both and boom, i again have a gui -- i don't know if i needed both

Re: X11 requirements list

On Thu, Jun 15, 2023 at 4:09 PM tooth pik wrote: > > some months ago i managed to break gvim messing around doing i wish i > remembered what, probably something to do with getting nvidia drivers to work > on my system > > for me vim no longer builds with X11, vim builds fine but no gui > > is

Re: Vim configured with both --with-features=normal and --enable-libsodium ends up with libsodium linked in but the +sodium feature disabled

On Mon, May 8, 2023 at 11:09 PM Bram Moolenaar wrote: [...] > This is indeed strange. The configure check for sodium defaults to only > checking when using "huge" features. That makes sense, it is something > advanced, not always needed. But in the src/feature.h file the > FEAT_HUGE macro is

Re: Same number different colors for ctermbg and ctermfg

On Thu, May 4, 2023 at 12:14 PM Enan Ajmain <3nan.ajm...@gmail.com> wrote: > > Hi, > > For the value 7, ctermfg and ctermbg gives different colors. 'ctermfg=7' > gives non-bold white, which is expected. But 'ctermbg=7' gives bold > Black color. I'm assuming there is a if-conditional somewhere

Re: Documentation update: How to set a font

On Sat, Apr 29, 2023 at 11:10 PM Bram Moolenaar wrote: […] > We don't support GTK 1 anymore, suggesting code in the help for not > implemented functionality doesn't make much sense. OK. Well, in that case we should test for "if has('gui_gtk')" (and not gtk2) rather high in the list, suppress the

Re: Documentation update: How to set a font

On Sat, Apr 29, 2023 at 7:02 PM Bram Moolenaar wrote: > > > Tony wrote: > > > Under *setting-guifont*, in file runtime/doc/gui.txt (or > > $VIMRUNTIME/doc/gui.txt) line 1229 > > there is > > if has("gui_gtk2") > > there should be > > if has("gui_gtk2") || has("gui_gtk3") > >

Documentation update: How to set a font

Under *setting-guifont*, in file runtime/doc/gui.txt (or $VIMRUNTIME/doc/gui.txt) line 1229 there is if has("gui_gtk2") there should be if has("gui_gtk2") || has("gui_gtk3") otherwise the 'guifont' option will be given a wrong font name (selected by has("x11")) in gvim with

Re: Compiler warnings in Vim with +eval and +gui_gtk after applying patches 1492 to 1496

On Sat, Apr 29, 2023 at 3:26 PM Bram Moolenaar wrote: > > > Tony wrote: > > > I'm including the full log because "make -j4" might display the > > warnings otherwise than where they belong. > > > > linux-tuxedo:~/.build/vim/vim-hg/src/shadow-normal # (make -j4 || echo > > 'exit status' $? ; date)

Compiler warnings in Vim with +eval and +gui_gtk after applying patches 1492 to 1496

I'm including the full log because "make -j4" might display the warnings otherwise than where they belong. linux-tuxedo:~/.build/vim/vim-hg/src/shadow-normal # (make -j4 || echo 'exit status' $? ; date) 2>&1 |tee -a make.log gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-3.0

Re: Finding the Motif libs

On Wed, Apr 12, 2023 at 6:09 PM Bram Moolenaar wrote: > > > Tony wrote: > > > > > According to the YaST installer, openSUSE Tumbleweed package libXm4 > > > > titled "Motif runtime library" installs (only) files > > > > /usr/lib64/libXm.so.4 and /usr/lib64/libXm.so.4.0.4 > > > > > > > > so I did >

Re: Finding the Motif libs

On Mon, Apr 10, 2023 at 9:07 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 > > > > following lines: > > > > > > > > checking --enable-gui

Re: Finding the Motif libs

On Mon, Apr 10, 2023 at 10:11 PM James McCoy wrote: > > 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: > > > > > > > Recen

Re: Finding the Motif libs

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 > > following lines: > > > > checking --enable-gui argument... Motif GUI

Finding the Motif libs

Recently (but I'm not sure when) my supposedly Motif gvim started getting compiled without GUI. Examination of the config log showed the following lines: checking --enable-gui argument... Motif GUI support checking for pkg-config... /usr/bin/pkg-config checking for location of Motif GUI

Re: using vim to run vim9script

On Wed, Mar 29, 2023 at 9:58 PM Ernie Rael wrote: [...] > The interesting thing is that if the vimscript > exits with an exception or :cquit, then after the bash shell > script exits, the return code is 1 (as hoped for), otherwise it > exits with 0. This seems to be undocumented behavior. [...]

Re: Compilation warnings in builds with expression evaluation

On Tue, Mar 28, 2023 at 6:25 PM Bram Moolenaar wrote: > > > Tony wrote: > > > I noticed this in a "make reconfig" at patchlevel 9.0.1429. It may or > > may not have happened earlier. Builds without expression evaluation > > are not affected. > > > > The following is from a Normal build without

Re: Warning (no error) in regexp.nfa.c included from regexp.c in Tiny build

On Sat, Mar 25, 2023 at 12:30 PM Bram Moolenaar wrote: > > > Tony wrote: > > > In file included from regexp.c:2707: > > regexp_nfa.c: In function ‘nfa_regmatch’: > > regexp_nfa.c:6696:33: warning: ‘bytelen’ may be used uninitialized > > [-Wmaybe-uninitialized] > > 6696 | if

Compilation warnings in builds with expression evaluation

I noticed this in a "make reconfig" at patchlevel 9.0.1429. It may or may not have happened earlier. Builds without expression evaluation are not affected. The following is from a Normal build without the -j argument to make, to avoid line-interlacing from builds of different modules: gcc -c -I.

Warning (no error) in regexp.nfa.c included from regexp.c in Tiny build

In file included from regexp.c:2707: regexp_nfa.c: In function ‘nfa_regmatch’: regexp_nfa.c:6696:33: warning: ‘bytelen’ may be used uninitialized [-Wmaybe-uninitialized] 6696 | if (bytelen == 0) | ^~~~ regexp_nfa.c:6679:21: note: ‘bytelen’

Re: doc: Spelling of LAMBDA in digraph table

On Tue, Mar 21, 2023 at 10:37 AM Max Mahlke wrote: > > Dear all, > > in runtime/doc/digraph.txt, the greek letter lambda is spelt LAMDA. I > was looking for it under the accepted spelling LAMBDA, though I am aware > that some people prefer the LAMDA spelling. I see that the vim source > makes

Confusing help

At change.txt lines 1382-1386: > If you use a put command without specifying a register, Vim uses the register > that was last filled (this is also the contents of the unnamed register). If > you are confused, use the `:dis` command to find out what Vim will put (this > command displays all

Re: Patch 9.0.1283

On Sun, Feb 5, 2023 at 5:03 PM Bram Moolenaar wrote: > > > Patch 9.0.1283 > Problem:The code for setting options is too complicated. > Solution: Refactor the do_set() function. (Yegappan Lakshmanan, Lewis > Russell, closes #11945) > Files: src/option.c Warnings

Re: "Connection refused" at hg.256bit.org

On Fri, Jan 20, 2023 at 8:58 PM Christian Brabandt wrote: > > Am 2023-01-20 16:53, schrieb Tony Mechelynck: > > The date-time stamps below (1. good, 2. bad) give a range of when it > > started to happen. "traceroute hg.256bit.org" seems to run OK. > > > &g

"Connection refused" at hg.256bit.org

The date-time stamps below (1. good, 2. bad) give a range of when it started to happen. "traceroute hg.256bit.org" seems to run OK. linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date comparing with http://hg.256bit.org/vim searching for changes no changes found (sent 2 HTTP

Build failure in Tiny (scroll_dict undefined at window.c:3137:27) after applying patches 9.0. 925 to 928

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/window.o window.c window.c: In function ‘may_trigger_win_scrolled_resized’: window.c:3137:27: error: ‘scroll_dict’ undeclared

Re: Health update

On Wed, Nov 2, 2022 at 1:00 PM Bram Moolenaar wrote: [...] > OK. Changing commits would be rewriting history, that sounds like > something we don't want, even though it looks like some commits were not > done right. I tried creating diffs from the tagged commits, but those > are a bit messy

Re: Christian, is your Mercurial server down?

t; > > > Best > > Chris > > > >> Am 31.10.2022 um 15:38 schrieb Tony Mechelynck > >> : > >> > >> For some reason after I have downloaded patches up to 9.0.818 (which > >> doesn't build) with the exception of patch 9.0.816

Christian, is your Mercurial server down?

For some reason after I have downloaded patches up to 9.0.818 (which doesn't build) with the exception of patch 9.0.816 (which apparently is missing) your Mercurial server http://hg.256bit.org/vim has been telling me (for some days already) that there are "no changes found". However I see in the

Re: Health update

On Fri, Oct 28, 2022 at 10:05 AM Bram Moolenaar wrote: [...] > Thanks for all the wishes, it helps a lot to know you are caring. Indeed we care. Take care of your health, and in the meantime we'll try to take care of Vim as best we can. Best regards, Tony. -- -- You received this message

Patch 9.0.816 missing?

"hg glog -l 10" gives me patches up to 9.0.814 and 9.0.815; "hg in" gives me patches 9.0.817 and 9.0.818 only. None of 815, 817 or 818 has either a Description (other than the patch number itself) or a tag on the Mercurial server. What happened to patch 816 "CTRL-Z at end of file is always

Strange patch 9.0.815

At least on the Mercurial server, patch 9.0.815 has no description of the "problem", nor of the "solution", and it also hasn't got a Mercurial tag. Neither does it have a vim-dev message AFAICT. Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not top-post!

Thanks Bram for re-enabling +rightleft +arabic

Thanks Bram for re-enabling +rightleft +arabic! I'll still be compiling 5 builds of Vim, some of them as a sanity test for various compile-time featuresets, as follows: • vi: a minimum build with as few features as possible and in particular -eval and no GUI • vim-small: a build with -eval but

Re: Cannot compile with +rightleft and +arabic

On Sun, Oct 9, 2022 at 12:45 PM Bram Moolenaar wrote: > It is rather arbitrary. I moved features related to highlighting to the > normal build, and features related to natural language support to the > huge build. Now we have three builds that are different enough to > justify their existence.

Re: Cannot compile with +rightleft and +arabic

On Sun, Oct 9, 2022 at 12:45 PM Bram Moolenaar wrote: > > > Tony wrote: > > > Whatever I do, my Vim executables come now out with -rightleft and > > -arabic (since patchlevel 700 maybe?). > > > > These features used to work well enough, and that is the reason why I > > haven't been filing bug

Cannot compile with +rightleft and +arabic

Whatever I do, my Vim executables come now out with -rightleft and -arabic (since patchlevel 700 maybe?). These features used to work well enough, and that is the reason why I haven't been filing bug reports or posting feedback about them. Now I see that at lines 237 to 247 of feature.h, both

Link error in Tiny build (undefined reference to `plines_nofill' in move.c in function `scroll_cursor_bot') after applying patches 9.0. 670 to 672

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/move.o move.c gcc

Re: Patch 9.0.0649

On Mon, Oct 3, 2022 at 5:44 PM Bram Moolenaar wrote: > > > Patch 9.0.0649 > Problem:No indication when the first line is broken for 'smoothscroll'. > Solution: Show "<<<" in the first line. > Files: src/drawline.c, src/testdir/dumps/Test_smoothscroll_2.dump, >

After ":set sms" in my .vimrc, 'smoothscroll' is not set in files edited later (Big gvim 9.0.643)

I added in my vimrc the lines if exists ('+smoothscroll') set sms endif (the :set line is line 299). After my handcrafted session file (sourced by invoking "gvim -S") loads several files with 'wrap' set (also by my vimrc) in gvim (Big) 9.0.643 I tried repeatedly hitting Ctrl-E in one of

Re: At patch level 9.0.471: Segmentation fault at startup

The problem disappears after "make reconfig". Library discrepancy between "recently changed" and "other" modules? (I'm on openSUSE Tumbleweed, a rather "volatile" OS.) Best regards, Tony. On Thu, Sep 15, 2022 at 8:48 PM Tony Mechelynck wr

At patch level 9.0.471: Segmentation fault at startup

• I only tested the Big version. • This happens in both vim and gvim. • With my usual handcoded Session file, it happens immediately in both vim and gvim. • With only my usual vimrc, it happens immediately in gvim; in vim the :info splash screen is displayed, then hitting Space a couple of times

Errors in $VIMRUNTIME/autoload/dist/ft.vim at patchlevel 9.0.376

This did not happen at patchlevel 372 Error detected while processing command line..script /root/Session.vim[12]..BufRead Autocommands for "*.htm"..script /usr/local/share/vim/vim90/autoload/dist/ft.vim: line 114: E15: Invalid expression: " '')" E475: Invalid argument: default = '') Error

-Wmaybe-uninitialized in Normal, Big and Huge spellfile.c after applying patches 9.0. 373 to 375

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 -I/usr/include/fribidi -I/usr/include/cairo

Re: Zero cmdheight

To each his choice. Personally I set 'cmdheight' to at least 2 to avoid it bobbing up and down too much; OTOH for the sake of screen space I set 'winminheight' to zero, 'winheight' to , 'helpheight' to and 'noequalalways', so all non-current windows get reduced to just a status line and

Re: [vim/vim] gvim --help does not show important information about configuration files (Issue #10999)

On Mon, Aug 29, 2022 at 8:39 AM Christian Brabandt < vim-dev-git...@256bit.org> wrote: > you can also check :version output: > [image: image] > > You can then use :e $HOME/vimfiles/vimrc to

Build failure in Small and Tiny cmdexpand.c after applying patches 9.0 276 to 280

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/cmdexpand.o

Re: Patch 9.0.0261

On Thu, Aug 25, 2022 at 1:46 PM Bram Moolenaar wrote: > > > Patch 9.0.0261 > Problem:bufload() reads a file even if the name is not a file name. (Cyker > Way) > Solution: Do not read the file when the buffer name is not a file name. > (closes #10975) > Files:

Re: Patch 9.0.0241

Ah, I see: Patch 242. On Sun, Aug 21, 2022 at 11:41 PM Tony Mechelynck wrote: > > On Sun, Aug 21, 2022 at 10:05 PM Bram Moolenaar wrote: > > > > > > Patch 9.0.0241 > > Problem:"make install" does not install shared syntax file. (James > >

Re: Patch 9.0.0241

On Sun, Aug 21, 2022 at 10:05 PM Bram Moolenaar wrote: > > > Patch 9.0.0241 > Problem:"make install" does not install shared syntax file. (James McCoy) > Solution: Install and uninstall the shared syntax files. (closes #10956) > Files: src/Makefile After this patch, "make install"

Re: Warning or error (depending on featureset) trying to build Vim 9.0.156 (after applying patches 151 to 156)

On Sat, Aug 6, 2022 at 11:37 PM Bram Moolenaar wrote: > > > Tony wrote: > > > In the Huge, Big and Normal builds I get -Wmaybe-uninitialized > > warnings for line_attr in drawline.c but they are different in each > > case; I don't understand getting a -Wmaybe-uninitialized for a > > variable

Warning or error (depending on featureset) trying to build Vim 9.0.156 (after applying patches 151 to 156)

In the Huge, Big and Normal builds I get -Wmaybe-uninitialized warnings for line_attr in drawline.c but they are different in each case; I don't understand getting a -Wmaybe-uninitialized for a variable which was given an initial value on the line declaring it. This is gcc 12.1.1 20220721: * In

Re: Patch 9.0.0121

On Sun, Jul 31, 2022 at 6:36 PM Bram Moolenaar wrote: > > > Patch 9.0.0121 > Problem:Cannot put virtual text after or below a line. > Solution: Add "text_align" and "text_wrap" arguments. > Files: runtime/doc textprop.txt, src/textprop.c, src/structs.h, > src/drawline.c,

Re: Patch 9.0.0072

On Tue, Jul 26, 2022 at 12:43 PM Bram Moolenaar wrote: > > > Tony wrote: > > > On Mon, Jul 25, 2022 at 10:16 PM Bram Moolenaar wrote: > > > > > > > > > Patch 9.0.0072 (after 9.0.0067) > > > Problem:Compiler warning for uninitialized variable. > > > Solution: Initialize it. (John Marriott)

Re: Patch 9.0.0072

On Mon, Jul 25, 2022 at 10:16 PM Bram Moolenaar wrote: > > > Patch 9.0.0072 (after 9.0.0067) > Problem:Compiler warning for uninitialized variable. > Solution: Initialize it. (John Marriott) > Files: src/drawline.c After this patch, I get a new warning in Big and Huge only, as

Warning in drawline.c after applying patches 9.0.67 to 71

The following (as shown for Big) also appears in Huge build: 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

Re: Patch 9.0.0033

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

Re: Patch 8.2.5148

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,

Re: Patch 8.2.5003

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,

  1   2   3   4   5   6   7   8   9   10   >