On Tue, Jul 15, 2025 at 8:13 AM Christian Brabandt wrote:
>
>
> On Mo, 14 Jul 2025, Tony Mechelynck wrote:
>
> > Are you sure you pushed it to https://www.vim.org/hgweb/vim/ ? "hg in"
> > gives me nothing new after the runtime files changeset which followed
>
On Mon, Jul 14, 2025 at 9:48 PM Christian Brabandt wrote:
>
>
> On Mo, 14 Jul 2025, Tony Mechelynck wrote:
>
> > After applying patches 1539 and 1540 I get the following in all builds
> > (Tiny, Normal and Huge):
> >
> > insexpand.c: In function ‘ins_compl
After applying patches 1539 and 1540 I get the following in all builds
(Tiny, Normal and Huge):
insexpand.c: In function ‘ins_compl_new_leader’:
insexpand.c:2459:9: warning: ‘save_w_wrow’ may be used uninitialized
[-Wmaybe-uninitialized]
2459 | show_pum(save_w_wrow, save_w_leftcol);
Mercurial changeset 333ccd1e9743 (corresponding to git changeset
7306e8fcdb6fd17276b6aafb23a522cefecb5857) adds patchlevel 1538 to
src/version.c but the corresponding tag is missing in .hgtags ; I
don't know about the git tag, bookmark, or whatever.
N.B. AFAICT this changeset otherwise only change
P.S. I found how to add +lua: apparently when upgrading lua
automatically from 3.13 to 3.14 package lua314-devel had not been
installed.
Best regards,
Tony.
On Mon, Jun 30, 2025 at 1:22 AM Tony Mechelynck
wrote:
>
> The gvim I normally use is "Huge without interpreted languages&qu
The gvim I normally use is "Huge without interpreted languages" but I
also compile a build "with languages" just in case I might have a use
for it. At the moment it has -lua -mzscheme +perl -python +python3
+ruby +tcl.
Maybe I should try to find how to build with +lua (IIRC some Wikipedia
template
Compile warning -Wmaybe-uninitialized in ex_cmds.c after applying
patches 9.1.1474 to 1478
On "make reconfig" in any build using gcc (SUSE Linux) 15.1.1 20250528:
ex_cmds.c: In function ‘ex_uniq’:
ex_cmds.c:838:24: warning: ‘save_c’ may be used uninitialized
[-Wmaybe-uninitialized]
838 |
The v9.1.1391 patch for src/version.c includes several changes, but it
does not add an additional patchlevel to the list static int
included_patches[] starting at new line 710, therefore the resulting
Vim identifies itself as revision 9.1.1390.
Best regards,
Tony.
--
--
You received this messag
On Fri, May 9, 2025 at 5:38 PM Tony Mechelynck
wrote:
>
> On Fri, May 9, 2025 at 10:55 AM Christian Brabandt wrote:
> >
> >
> > On Fri, 09 May 2025, Tony Mechelynck wrote:
> >
> > > On Fri, May 9, 2025 at 7:54 AM Tony Mechelynck
> > > wrote:
>
On Fri, May 9, 2025 at 10:55 AM Christian Brabandt wrote:
>
>
> On Fri, 09 May 2025, Tony Mechelynck wrote:
>
> > On Fri, May 9, 2025 at 7:54 AM Tony Mechelynck
> > wrote:
> > >
> > > Since a few days, while sourcing the following session file:
> >
line, but no more than one line of edit window (or is
it an empty status line ?) above it
On Fri, May 9, 2025 at 10:56 AM Christian Brabandt wrote:
>
> Hi,
> Can you both please respond to the mentioned ticket? Is this that bad,
> that we need to revert?
>
> Thanks,
> Chris
P.S. Oh, and X11, I don't use Wayland.
Best regards,
Tony.
On Fri, May 9, 2025 at 9:58 AM Tony Mechelynck
wrote:
>
> This seems to be the same problem as the one I reported a few minutes
> ago as «"E36 Not enough room" while sourcing handcrafted session
> file». I am
This seems to be the same problem as the one I reported a few minutes
ago as «"E36 Not enough room" while sourcing handcrafted session
file». I am now with gvim 9.1.1374 but it has been happening for a
couple of days in earlier versions. Huge version with GTK3 GUI. The
GUI opened with just enough h
On Fri, May 9, 2025 at 7:54 AM Tony Mechelynck
wrote:
>
> Since a few days, while sourcing the following session file:
>
> " Vim session file
> " This one was not generated by :mksession.
>
> " e ~/.mozilla/seamonkey/eiox68r9.default/user.js
> e ~/.mozil
On Sat, Apr 26, 2025 at 8:03 PM Christian Brabandt wrote:
>
>
> On Fri, 25 Apr 2025, Tony Mechelynck wrote:
>
> > I'm giving below my "last good" and "first bad" attempts at
> > connection. This is still happening at 2025-04-25 23:15 Belgian
I'm giving below my "last good" and "first bad" attempts at
connection. This is still happening at 2025-04-25 23:15 Belgian summer
time (UTC+0200).
linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
comparing with https://www.vim.org/hgweb/vim/
searching for changes
no change
In function ‘ins_compl_build_pum’,
inlined from ‘ins_compl_show_pum’ at insexpand.c:1668:8,
inlined from ‘ins_compl_show_pum’ at insexpand.c:1654:1:
insexpand.c:1520:52: warning: ‘match_count’ may be used uninitialized
[-Wmaybe-uninitialized]
1520 | if (max_matches > 0 && m
In function ‘cpt_compl_refresh’,
inlined from ‘ins_compl_new_leader’ at insexpand.c:2218:6:
insexpand.c:6450:16: warning: ‘cb’ may be used uninitialized
[-Wmaybe-uninitialized]
6450 | if (cb)
|^
insexpand.c: In function ‘ins_compl_new_leader’:
insexpand.c:6430
AFAICT patchlevel 9.1.1253 is mentioned neither in src/version.c nor
in .hgtags. I suppose this "weirdness" is due to distraction and can
be left as-is.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are reply
On Mon, Feb 3, 2025 at 2:00 AM Michael Scheper
wrote:
>
> I'm trying to install gVim 9 on Mint 21.3 Cinnamon.
>
> configure complained about a missing library, and sudo apt install
> libncurses-dev made that go away. Then, after I complied it using make, vim
> worked great… but gvim was missing
Among my several shadow builds of Vim, I used to compile one with
+python (i.e. Python 2) -python3. Today with no change in my
configuration it came back with -python -python3. AFAICT package
python-devel has been dropped by my openSUSE Tumbleweed distro. After
installing python311-devel and changi
I notice three kinds of answers in this thread :
• Always use defaults.vim regardless of whether there is a vimrc.
• Never use defaults.vim, i.e. go back to prehistory when even
vimrc_example.vim didn't exist.
• Use defaults.vim by default when no vimrc is found, unless it is
explicitly disabled by
On Sun, Jan 19, 2025 at 11:37 PM Christian Brabandt wrote:
>
> Note: I am not sure yet how well the hg bridge will be working on the
> new server. I need to monitor it a bit for the future. Hopefully it will
> work fine however.
>
> On Sun, 19 Jan 2025, Tony Mechelynck wro
On Sun, Jan 19, 2025 at 10:44 PM Tony Mechelynck
wrote:
>
> On Sun, Jan 19, 2025 at 10:29 PM Christian Brabandt
> wrote:
> >
> >
> > On Mon, 13 Jan 2025, Tony Mechelynck wrote:
> >
> > > P.S. When I try "hg in" from http://hg.vim.org/ (my n
On Sun, Jan 19, 2025 at 10:29 PM Christian Brabandt wrote:
>
>
> On Mon, 13 Jan 2025, Tony Mechelynck wrote:
>
> > P.S. When I try "hg in" from http://hg.vim.org/ (my new default server
> > address) I get 403 Forbidden, and from hg://256bit.org/vim (which I
>
On Sun, Jan 19, 2025 at 9:56 PM Eric Pruitt wrote:
>
> On Sun, Jan 12, 2025 at 04:33:28PM +0100, Tony Mechelynck wrote:
> > So I'm faced with a dilemma : either remain (maybe forever) with the
> > 9.1.873 which I configured myself and didn't change since your
> &
On Sun, Jan 12, 2025 at 8:23 PM Christian Brabandt wrote:
[…]
> It's great to be smart 'cause then you know stuff.
The advantage of being smart is that you can play dumb. The opposite
is totally impossible.
— Attributed to Woody Allen.
--
--
You received this message from the "vim_dev" maillis
P.S. When I try "hg in" from http://hg.vim.org/ (my new default server
address) I get 403 Forbidden, and from hg://256bit.org/vim (which I
just tried, just in case) I get 404 Not found.
Best regards,
Tony.
On Sun, Jan 12, 2025 at 8:23 PM Christian Brabandt wrote:
>
>
> On Sun
Hi Christian,
Last night openSUSE Tumbleweed has updated more than 9000 packages,
and their Vim is now at version 9.1.993; but of course it is not
exactly configured the way I'd like it. So I'm faced with a dilemma :
either remain (maybe forever) with the 9.1.873 which I configured
myself and didn
I see several threads aguing in favour of a change of Vim's defaults.
I believe that such changes are unwise, and here is why :
At the moment, there are several sets of "default" option settings in Vim :
- "compatible" defaults (or "vi defaults") used when the -C switch
is used on the command-li
I'm still further ahead than behind, so no hurry yet:
Vim from my openSUSE distro: 9.1.836
-- 37 patchlevels
Vim I compiled myself when the Mercurial server was still online: 9.1.873
-- 22 patchlevels
Latest Vim as posted on vim-dev: 9.1.895
so my best choice is still my own-compiled Vim (wit
On Thu, Nov 21, 2024 at 3:33 PM Marvin Renich wrote:
>
> * Tony Mechelynck [241121 00:10]:
> > On Wed, Nov 20, 2024 at 7:48 PM Marvin Renich wrote:
> > > I have, in the past, used the hggit extension
> > > (https://hg-git.github.io/), rather than the git exten
On Wed, Nov 20, 2024 at 7:48 PM Marvin Renich wrote:
>
> * Tony Mechelynck [241120 04:27]:
> > The "official" solution, if the Mercurial server is retired forever,
> > is to use git instead, but to at least one of us (me) and possibly
> > more, git is so foreig
On Wed, Nov 20, 2024 at 11:10 AM Christian Brabandt wrote:
>
>
> On Wed, 20 Nov 2024, Christian Brabandt wrote:
>
> >
> > On Wed, 20 Nov 2024, Tony Mechelynck wrote:
> >
> > > On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt
> > > wrote:
> &
The "official" solution, if the Mercurial server is retired forever,
is to use git instead, but to at least one of us (me) and possibly
more, git is so foreign that we would rather explore all other
possible solutions before resorting to it. This message is written by
and for this kind of user.
So
P.S.
On Wed, Nov 20, 2024 at 10:49 AM Tony Mechelynck
wrote:
>
> On Wed, Nov 20, 2024 at 10:34 AM Christian Brabandt
> wrote:
> […]
> > Oh, Apparently I am still pushing to osdn, I thought I had disabled this
> > long time ago. For the time being, you can continue to u
On Wed, Nov 20, 2024 at 10:34 AM Christian Brabandt wrote:
[…]
> Oh, Apparently I am still pushing to osdn, I thought I had disabled this
> long time ago. For the time being, you can continue to use that one.
[…]
I would, if it would let me ; but AFAICT Mercurial is adamant about
not letting me p
someone at the
receiving end like me it would just be a matter of adjusting the
source aliases (i.e. those displayed by "hg paths") to make sure that
the "default" source is the one we normally want to pull from. A piece
of cake.
>
> Thanks,
> Chris
My pleasure,
To
On Wed, Nov 20, 2024 at 2:10 AM Tony Mechelynck
wrote:
>
> On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt wrote:
> >
> > Hi,
> > just to let everybody know. Because of serious load issues, the HG
> > bridge is disabled for now.
> >
> > Just for my re
On Tue, Nov 19, 2024 at 2:55 PM Christian Brabandt wrote:
>
>
> On Tue, 19 Nov 2024, Tony Mechelynck wrote:
>
> > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > abort: error: Connection refused
> > exit status 255
> >
linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
abort: error: Connection refused
exit status 255
Tue 19 Nov 14:48:32 CET 2024
linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
abort: error: Connection refused
exit status 255
Tue 19 Nov 14:48:50 CET 20
On Thu, Nov 14, 2024 at 8:59 AM Christian Brabandt wrote:
>
>
> On Do, 14 Nov 2024, Tony Mechelynck wrote:
>
> > The following has now been fixed.
> >
> > On Wed, Nov 13, 2024 at 9:46 PM Tony Mechelynck
> > wrote:
> > >
> > > Trying to pull
The following has now been fixed.
On Wed, Nov 13, 2024 at 9:46 PM Tony Mechelynck
wrote:
>
> Trying to pull from http://hg.256bit.org/vim (which worked previously)
>
> linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> abort: error: Connection ti
Trying to pull from http://hg.256bit.org/vim (which worked previously)
linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
abort: error: Connection timed out
exit status 255
Wed 13 Nov 21:32:50 CET 2024
linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
a
On Mon, Aug 26, 2024 at 3:15 AM Tony Mechelynck
wrote:
>
> On Sat, Aug 24, 2024 at 4:24 PM Christian Brabandt wrote:
> >
> >
> > On Fr, 23 Aug 2024, Tony Mechelynck wrote:
> >
> > > Hello, I just noticed that the module gui_xim.c is included even in
>
On Sat, Aug 24, 2024 at 4:24 PM Christian Brabandt wrote:
>
>
> On Fr, 23 Aug 2024, Tony Mechelynck wrote:
>
> > Hello, I just noticed that the module gui_xim.c is included even in
> > Vim without GUI, where AFAICT no other GUI module is compiled-in. Is
> > this
On Sun, Aug 25, 2024 at 8:30 PM Christian Brabandt wrote:
>
> patch 9.1.0696: installing runtime files fails when using SHADOWDIR
>
> Commit:
> https://github.com/vim/vim/commit/663950d700f496c1db09307253e6b1b2a56140d5
> Author: James McCoy
> Date: Sun Aug 25 20:22:11 2024 +0200
>
> patch
Hello, I just noticed that the module gui_xim.c is included even in
Vim without GUI, where AFAICT no other GUI module is compiled-in. Is
this normal ?
Here is the configuration for my Tiny build without GUI (the
src/Makefile is unchanged from the distribution and the
src/shadow-tiny/Makefile resen
On Sat, Jul 13, 2024 at 5:03 AM Tony Mechelynck
wrote:
>
> hg in || echo "exit status" $? ; date
> abort: error: Connection timed out
> exit status 255
> Sat 13 Jul 04:51:13 CEST 2024
>
> Best regards,
> Tony.
Works for me now (13:06 CEST)
Best regards,
Tony.
hg in || echo "exit status" $? ; date
abort: error: Connection timed out
exit status 255
Sat 13 Jul 04:51:13 CEST 2024
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, visi
On Wed, May 22, 2024 at 5:00 PM Christian Brabandt wrote:
>
> patch 9.1.0432: Ancient XPM preprocessor hack may cause build errors
>
> Commit:
> https://github.com/vim/vim/commit/5090f838bbcd3a13433d9fe20a94f3ce6b796eb1
> Author: Drew Vogel
> Date: Wed May 22 16:51:53 2024 +0200
>
> patch
On Tue, May 14, 2024 at 4:10 AM Michael Soyka wrote:
>
> Chris,
>
> Thank you for the explanation but I don't think it explains everything.
> See below.
>
> On 05/13/2024 4:15 PM, Christian Brabandt wrote:
> > On Mo, 13 Mai 2024, Michael Soyka wrote:
> >
> >> Yes, your are right- the bwipeout comm
On Sun, May 12, 2024 at 12:15 AM Christian Brabandt wrote:
>
> patch 9.1.0409: too many strlen() calls in the regexp engine
>
> Commit:
> https://github.com/vim/vim/commit/82792db6315f7c7b0e299cdde1566f2932a463f8
> Author: John Marriott
> Date: Sun May 12 00:07:17 2024 +0200
>
> patch 9.1.
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
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
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 o
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 f
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);
|
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
[…]
Th
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 hav
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,
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, o
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
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
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 |
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)
> >
> >
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 + mo
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
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
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 |
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
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 metadata
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
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 vim on sam
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
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 ‘e_abstract_must_be_followed_by_
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 AFAI
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 thi
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 -fno-str
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
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]
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 http://www.vim.org/maillist.ph
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
Go
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
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 memories
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,
> > cur
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 programm
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.
> > >
> >
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 :
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 m
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
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:
> > >
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
> >
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 change
• 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 exists(':t
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:
gc
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
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 th
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 ch
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 tha
1 - 100 din 1888 matches
Mail list logo
