Bram, did the message below fall off your radar? AFAICT the warning
(in +eval builds) is still extant.
Best regards,
Tony.
On Sun, May 24, 2020 at 1:47 PM Tony Mechelynck
wrote:
>
> On Sun, May 24, 2020 at 1:11 PM Bram Moolenaar wrote:
> >
> >
> > Patch 8.2.0815
>
On Mon, May 25, 2020 at 2:15 AM Yegappan Lakshmanan wrote:
>
> Hi,
>
> To clear the contents of a list named "abc", we can use "unlet abc[:]".
> It looks like a similar method for clearing the contents of a dictionary
> is not available. We can set the dictionary variable to another empty
>
On Sun, May 24, 2020 at 1:11 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.0815
> Problem:maparg() does not provide enough information for mapset().
> Solution: Add "lhsraw" and "lhsrawalt" items. Drop "simplified"
> Files: src/map.c, runtime/doc/eval.txt, src/testdir/test_maparg.vim
This
In addition to what Gary said, I'd mention that binary files (files read
with e.g. :e ++bin filename.ext) and files where ":setlocal nofixeol" has
been set (which is not the default) will be written with an incomplete last
line if 'noeol' was set either at read-time (because no EOL was found on
On Fri, May 22, 2020 at 1:11 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.0807
> Problem:Cannot easily restore a mapping.
> Solution: Add mapset().
> Files: runtime/doc/eval.txt, src/map.c, src/proto/map.pro, src/evalfunc.c
> src/testdir/test_maparg.vim
Missing #ifdef ? I get
Suddenly I notice the menu on top of my gvim screen has disappeared.
(The toolbar is still there with its icons and their menus. The popup
menu also appears on right-click. Only the main menu is gone.)
Don't know if it's the fact of compiling with GTK3 instead of GTK2, ot
of switching from KDE
On Sun, May 17, 2020 at 9:40 PM Charles Campbell wrote:
>
> Hello:
>
> I seem to have a problem doing git pull:
>
> fatal: Not a git repository (or any parent up to mount point /home)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM
> not set).
>
> Fortunately git
On Sun, May 17, 2020 at 5:12 PM Tony Mechelynck
wrote:
>
> On Sun, May 17, 2020 at 3:42 PM Ken Takata wrote:
> >
> > Hi Tony,
> > gui_mch_flash() is not implemented for GTK3:
> > https://github.com/vim/vim/blob/ed37d9b3241abe7c302c7ac606df80037aecdb46
On Sun, May 17, 2020 at 3:42 PM Ken Takata wrote:
>
> Hi Tony,
> gui_mch_flash() is not implemented for GTK3:
> https://github.com/vim/vim/blob/ed37d9b3241abe7c302c7ac606df80037aecdb46/src/gui_gtk_x11.c#L5941-L5943
>
> Regards,
> Ken Takata
>
Hm. There is a
// TODO Replace GdkGC with
gvim 8.2.773 (Big) with GTK3 GUI
:echo exists('+errorbells') exists('+visualbell') answers 1 1
My vimrc includes the following:
if exists('+errorbells') && exists('+visualbell')
set errorbells visualbell
if has('gui_running')
au GUIEnter * set t_vb= ^[\|250f
endif
endif
(in
On Sun, May 10, 2020 at 11:42 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > I notice that src/po/nb.po and src/po/no.po are identical, and both in
> > "Bokmål" Norwegian while "Nynorsk" Norwegian is not included. Is this
> > intentional? (On some softwares these "two official languages" of
> >
I notice that src/po/nb.po and src/po/no.po are identical, and both in
"Bokmål" Norwegian while "Nynorsk" Norwegian is not included. Is this
intentional? (On some softwares these "two official languages" of
Norway are included as nb_NO and nn_NO respectively; but when
"Norwegian" is taught to
When built with GTK2+GNOME2, Vim would (IIUC) save its session when
"unusually" terminated. However, GTK2 is at EOL and causes (in my new
version of the OS, viz. openSUSE 15.2 beta) warning messages in every
module in every +gui_gtk2 build, so I've gone over to GTK3. I notice that
my GTK3 build
On Wed, May 6, 2020 at 8:34 PM James McCoy wrote:
>
> 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
>&
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 module). The link phase runs in all
cases, and produces an
On Sat, May 2, 2020 at 6:05 PM Gary Johnson wrote:
>
> With the current code, you cannot have both the search stats ([1/5]
> count) and the BOTTOM/TOP message enabled at the same time.
>
> I looked into fixing that, but the main problem was that the text in
> the command line is in a global
On Sat, May 2, 2020 at 10:45 AM Christian Brabandt wrote:
>
> I think you need the S flag in shortmess
Well, if I add it, the message reappears; and yet, that "big S" flag
is supposed to suppress the [1/5] count when searching, so how can I
keep that message and _also_ have the BOTTOM/TOP
I just noticed that neither the "search hit BOTTOM, continuing at TOP"
message, nor the converse when searching backwards, are ever given
anymore; and yet I have 'shortmess' set to filnxtToO i.e. without the
s flag which is supposed to suppress that message. Is this intended?
I also helpgrepped
On Fri, May 1, 2020 at 5:52 PM Yegappan Lakshmanan wrote:
>
> Hi all,
>
> Currently we have the line(), col(), virtcol() and getpos() functions
> to get the position of a particular mark. But we don't have a
> function to get the list of local/global marks (information displayed
> by the :marks
On Fri, May 1, 2020 at 2:37 PM Christian Brabandt wrote:
> Oh vim can resize the terminal? Wow did not know that.
>
Some of them (such as a true xterm) it can, at least if they aren't
"maximized" from the winmanager's point of view. Others (such as konsole)
it can't, even if unmaximized. Of
On Wed, Apr 29, 2020 at 11:17 PM Bram Moolenaar wrote:
> Oops, forgot to diff against the clean file.
Indeed, patch 664 makes my compilation warnings disappear.
This is one of the risks one runs when using a modified Makefile.
Maybe you should set your configure arguments by means of
On Wed, Apr 29, 2020 at 9:04 PM Bram Moolenaar wrote:
>
>
> Patch 8.2.0660
> Problem:The search.c file is a bit big.
> Solution: Split off the text object code to a separate file. (Yegappan
> Lakshmanan, closes #6007)
> Files: Filelist, src/Make_cyg_ming.mak,
On Wed, Apr 15, 2020 at 9:06 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > After sending a message to the address vim-p...@googlegroups.com
> > mentioned as "maintainer" at top of the Perl ftplugin
> > $VIMRUNTIME/ftplugin/perl.vim I got the message below. IIUC this means
> > that the
After sending a message to the address vim-p...@googlegroups.com
mentioned as "maintainer" at top of the Perl ftplugin
$VIMRUNTIME/ftplugin/perl.vim I got the message below. IIUC this means
that the maintainer address should be changed. The syntax and indent
perl.vim scripts, as well as all three
On Thu, Apr 9, 2020 at 5:32 PM Yegappan Lakshmanan wrote:
>
> Hi all,
>
> The submatch() function with a second argument set to 1, returns NULL
> when used outside of a :substitute command or the substitute() function.
> All the other functions that return a List, return an empty List on failure.
I think that in the first case the original line was correct: a
twenty-minute training, a ten-kilometre distance, a ten-foot pole,
etc.: in English the unit of measure remains (IIRC) invariable (i.e.
does not take the mark of the plural) when used with a number before
the measured noun.
Native
Yeah, I see similar errors in Big and Normal, but not in Huge, Small
and Tiny, as follows. My Huge build is the only one with +terminal:
linux-2iyu:~/.build/vim/vim-hg/src/shadow-big # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
On Sun, Mar 22, 2020 at 5:24 PM Tony Mechelynck
wrote:
>
> At version 8.2.427 or later, it is possible to test if a feature could
> have been included in a different build. What about retired features,
> e.g. "farsi"?
>
> Nowadays,
> has('farsi')
&
At version 8.2.427 or later, it is possible to test if a feature could
have been included in a different build. What about retired features,
e.g. "farsi"?
Nowadays,
has('farsi')
always returns 0 no matter how the executable was configured.
It is not clear to me whether
On Thu, Mar 12, 2020 at 8:05 AM Christian Brabandt wrote:
>
>
> On Mi, 11 Mär 2020, Tony Mechelynck wrote:
>
> > This is what I see on the console:
> >
> > linux-2iyu:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > abort: error: Connection t
Update: Problem has now disappeared.
Best regards,
Tony.
On Wed, Mar 11, 2020 at 9:28 PM Tony Mechelynck
wrote:
>
> This is what I see on the console:
>
> linux-2iyu:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> abort: error: Connection timed out
> exit statu
This is what I see on the console:
linux-2iyu:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
abort: error: Connection timed out
exit status 255
Wed 11 Mar 20:10:27 CET 2020
linux-2iyu:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
abort: error: Connection timed out
exit
On Wed, Feb 19, 2020 at 5:46 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > I suggest adding feature 'vim9' testable by has()
> >
> > This is for consistency, it is not absolutely necessary since ":if
> > exists(':vim9script') == 2" should give the same result.
> >
> > I suppose the following
I suggest adding feature 'vim9' testable by has()
This is for consistency, it is not absolutely necessary since ":if
exists(':vim9script') == 2" should give the same result.
I suppose the following is an oversight: In my current 8.2.279 builds,
exists(':vim9script') returns 2 in the Huge build
At lines 234sqq of vim9.txt:
When {return-type} is omitted the return type will be
decided upon by the first encountered `return`
statement in the function. E.g., for: >
return 'message'
On Tue, Jan 28, 2020 at 8:51 PM Pavol Juhas wrote:
>
> Hello,
>
> I am using a fairly recent XTerm(348) on Debian linux.
> I have noticed that the modifyOtherKeys feature in vim
> makes mappings of meta keys (produced with Alt modifier)
> work out of the box, for example, `map :echo "meta-a"`.
>
On Mon, Jan 27, 2020 at 10:11 PM Bram Moolenaar wrote:
> This works fine on CI, did you not include all the changes?
> Especially check 8.2.0154.
Apparently I made hard links instead of soft links when adding the new
vim9* sources to my shadow directories. My bad.
Best r'egards,
Tony.
--
--
Except in Tiny and Small, I get a lot of warnings, and finally an
error makes gcc give up:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/pixman-1
On Sun, Jan 26, 2020 at 6:57 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > IIUC, the following is now a valid construct in newly-written or
> > updated non-"vim9script" script? (Let's say, a .vimrc which must also
> > support an older Vim version from my Linux distro)
> >
> > if
On Sun, Jan 26, 2020 at 6:18 PM Tony Mechelynck
wrote:
>
> IIUC, the following is now a valid construct in newly-written or
> updated non-"vim9script" script? (Let's say, a .vimrc which must also
> support an older Vim version from my Linux distro)
>
> if exi
IIUC, the following is now a valid construct in newly-written or
updated non-"vim9script" script? (Let's say, a .vimrc which must also
support an older Vim version from my Linux distro)
if exists('vim9script') == 2
import MyFunc as myfunc from '~/.vim/myvim9.vim'
else
function
In Tiny and Small:
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
On Tue, Dec 31, 2019 at 3:48 AM Ernie Rael wrote:
>
> On 12/30/2019 6:42 PM, Tony Mechelynck wrote:
> > On Tue, Dec 31, 2019 at 3:31 AM Ernie Rael wrote:
> >> On 12/29/2019 6:11 PM, Ernie Rael wrote:root
> >>> From python, is it *always* tru
On Tue, Dec 31, 2019 at 3:31 AM Ernie Rael wrote:
>
> On 12/29/2019 6:11 PM, Ernie Rael wrote:root
> > From python, is it *always* true that "vim.buffer[i].number == i" ?
> >
> > -ernie
> >
> I've convinced myself that this is true. The docs say
>
> A mapping object providing access to the
This is probably no problem, but…
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/scriptfile.o
scriptfile.c
scriptfile.c: In function ‘estack_sfile’:
scriptfile.c:102:10: warning: unused variable ‘done’
On Wed, Dec 18, 2019 at 11:10 PM Gary Johnson wrote:
>
> On 2019-12-18, Andy Massimino wrote:
> > Please don't change endfunction/endif/endwhile... it makes it hard for
> > plugins
> > like match-up to make % work. Also complicates things for very little
> > benefit,
> > at best saving a tiny
On Sat, Dec 14, 2019 at 3:45 PM Igor wrote:
>
> Vim 8.2.0003 on Linux.
>
> Having a text:
> aaa
> bbb
> and cursor in first line and join the lines with J normal mode ommand and the
> result is:
> aaa bbb
> as expected.
>
> But if there is full-stop character at the end of first line:
> aaa.
>
On Thu, Dec 12, 2019 at 7:38 PM Christian J. Robinson wrote:
>
> On Thu, 12 Dec 2019, Christian J. Robinson wrote:
>
> > :echo v:version
> > 801
> >
> > This happens in my manually compiled version and in the Windows
> > executable I got from vim.org.
>
> Correction, this does NOT happen with the
Some features, which are no longer supported, are listed under
|+feature-list| as if they were: for instance +farsi is listed as B
and +tag_old_static is listed as N. I suggest adding an additional
symbol in the left margin for "never (no longer supported)" (I propose
a dash, which would rank
Patch 8.1.2352 is not mentioned in src/version.c. This is not really a
problem, since this patch touches only .cirrus.yml and README.md, so
it affects neither the Vim executable nor even the runtime files; but
a Vim built from a repository containing that patch will have (for
instance) the
P.S. This seems to be (haven't pulled it yet) what 8.1.2332 aims to fix.
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
On Thu, Nov 21, 2019 at 10:15 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.2331
> Problem:The option.c file is still very big.
> Solution: Move a few functions to where they fit better. (Yegappan
> Lakshmanan, closes #4895)
> Files: src/option.c, src/proto/option.pro,
regards,
Tony.
On Thu, Nov 14, 2019 at 7:57 AM Tony Mechelynck
wrote:
>
> On Thu, Nov 14, 2019 at 6:56 AM Denis Krivosheev wrote:
> >
> > According to the official Dutch-Russian transliteration, double vowel
> > letters in Dutch are transmitted as single in Russian.
>
On Thu, Nov 14, 2019 at 6:56 AM Denis Krivosheev wrote:
>
> According to the official Dutch-Russian transliteration, double vowel letters
> in Dutch are transmitted as single in Russian.
>
> Wikipedia:
>
Warning in move.c in Tiny and Small after applying patches 8.1.2274 to .2283
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/move.o move.c
move.c: In function ‘curs_columns’:
move.c:991:14: warning: unused variable
Warning at line 3095 of buffer.c in Normal, Big and Huge after
applying patches 8.1.2257 to .2266:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
On Sun, Nov 3, 2019 at 9:47 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.2249
> Problem:"make vimtags" does not print any message.
> Solution: Add a message that the tags have been updated.
> Files: runtime/doc/Makefile
Thanks, I like this better.
And BTW I went back to the src/Makefile
On Sun, Nov 3, 2019 at 9:25 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > On Sun, Nov 3, 2019 at 6:39 PM Bram Moolenaar wrote:
> > >
> > >
> > > Patch 8.1.2247
> > > Problem:"make vimtags" does not work in runtime/doc.
> > > Solution: Test existence with "which" instead of "test -x".
On Sun, Nov 3, 2019 at 6:39 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.2247
> Problem:"make vimtags" does not work in runtime/doc.
> Solution: Test existence with "which" instead of "test -x". (Ken Takata)
> Files: runtime/doc/Makefile
Vim is still not run, not even after "touch
On Sun, Nov 3, 2019 at 5:42 PM Ken Takata wrote:
>
> Hi,
>
> 2019/11/4 Mon 0:50:37 UTC+9 Tony Mechelynck wrote:
>>
>> After recompiling just 8.1.2245 there were no changes to the docs, so
>> when running "make install" after that, runtime/doc/Makef
After recompiling just 8.1.2245 there were no changes to the docs, so
when running "make install" after that, runtime/doc/Makefile target
"vimtags" did nothing; yet at that point (runtime/doc/Makefile line
325 or src/Makefile line 2373) 25 or so empty lines were written on
the console. I'm
On Sat, Nov 2, 2019 at 10:46 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.2242
> Problem:Creating docs tags uses user preferences. (Tony Mechelynck)
> Solution: Add "--clean".
> Files: runtime/doc/Makefile
After applying this patch, as well as 2243 and 2
On Sat, Nov 2, 2019 at 10:15 PM Tony Mechelynck
wrote:
>
> On Sat, Nov 2, 2019 at 10:01 PM Bram Moolenaar wrote:
> >
> >
> > Tony wrote:
> >
> > > > > After the latest runtime files update, this problem has disappeared;
> > > > > but
On Sat, Nov 2, 2019 at 10:01 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > > > After the latest runtime files update, this problem has disappeared;
> > > > but helptags generation ("/usr/local/bin/vim -eX -u doctags.vim")
> > > > still outputs a large number of empty lines, which is annoying.
P.S. For some reason I don't see these many empty lines when running
"make install" after building with patch 8.1.2239.
Best regards,
Tony.
On Sat, Nov 2, 2019 at 6:24 PM Tony Mechelynck
wrote:
>
> On Sat, Nov 2, 2019 at 6:14 PM Bram Moolenaar wrote:
> >
> >
>
On Sat, Nov 2, 2019 at 6:14 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > After the latest runtime files update, this problem has disappeared;
> > but helptags generation ("/usr/local/bin/vim -eX -u doctags.vim")
> > still outputs a large number of empty lines, which is annoying. Would
> > it
After the latest runtime files update, this problem has disappeared;
but helptags generation ("/usr/local/bin/vim -eX -u doctags.vim")
still outputs a large number of empty lines, which is annoying. Would
it please be possible to filter them out (maybe 2>&1 | egrep -v ^\s*$
or something)?
Best
On Fri, Nov 1, 2019 at 7:47 PM Bram Moolenaar wrote:
> Patch 8.1.2238
> Problem:Error in docs tags goes unnoticed.
> Solution: Adjust tags build command. (Ken Takata, closes #5158)
> Files: Filelist, .travis.yml, runtime/doc/Makefile,
> runtime/doc/doctags.vim
Error
On Tue, Oct 29, 2019 at 4:50 AM Tony Mechelynck
wrote:
>
> On Tue, Oct 29, 2019 at 12:50 AM Bram Moolenaar wrote:
> >
> >
> > Patch 8.1.2232
> > Problem:MS-Windows: compiler warning for int size.
> > Solution: Add type cast. (Mike Williams)
> &g
On Tue, Oct 29, 2019 at 12:50 AM Bram Moolenaar wrote:
>
>
> Patch 8.1.2232
> Problem:MS-Windows: compiler warning for int size.
> Solution: Add type cast. (Mike Williams)
> Files: src/normal.c
This patch didn't make it to the Mercurial mirror, where 8.1.2231 "not
easy to move to the
On Sun, Oct 27, 2019 at 8:57 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > On Sun, Oct 27, 2019 at 7:00 PM Bram Moolenaar wrote:
> > >
> > > I wrote:
> > >
> > > > Patch 8.1.2226
> > > > Problem:Cannot use system copy/paste in non-xterm terminals.
> > > > Solution: Instead of setting
On Sun, Oct 27, 2019 at 7:00 PM Bram Moolenaar wrote:
>
>
> I wrote:
>
> > Patch 8.1.2226
> > Problem:Cannot use system copy/paste in non-xterm terminals.
> > Solution: Instead of setting 'mouse' to "a" set it to "nvi" in
> > defaults.vim.
> > Files:runtime/defaults.vim,
To set the n suboption in 'viminfo', RTFM:
- :help 'viminfo'
- :help :set
- :h :set+=
tl;dr: :set vi+=n/full/path/to/.viminfo
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
On Sun, Oct 27, 2019 at 4:37 PM Sihera Andre wrote:
>
> Hi Dominique,
>
>
> On 26/10/2019 19:10, Dominique Pellé wrote:
> > Sihera Andre wrote:
> >
> >> Hi Christian,
> >>
> >>
> >> On 25/10/2019 17:53, Christian Brabandt wrote:
> >>> On Fr, 25 Okt 2019, Sihera Andre wrote:
> >>>
> The
On Sat, Oct 26, 2019 at 12:18 AM John Marriott
wrote:
>
> Hi all,
>
> After this patch, mingw64 throws this warning if FEAT_TEXT_PROP is not
> defined:
> gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603
> -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -DFEAT_GUI_MSWIN
>
I've been sending mail to the wrong address. Too little coffee or too
little sleep. Going to bed now, I'll check later today if you two have
got the problem ironed out.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
On Fri, Oct 25, 2019 at 7:36 AM Sihera Andre wrote:
>
> Hi Tony,
>
>
> On 25/10/2019 13:55, Tony Mechelynck wrote:
> > On Fri, Oct 25, 2019 at 6:31 AM Sihera Andre
> > wrote:
> >> On 25/10/2019 13:06, Andre Sihera wrote:
> >>> Hello all,
>
On Fri, Oct 25, 2019 at 6:31 AM Sihera Andre wrote:
>
> On 25/10/2019 13:06, Andre Sihera wrote:
> > Hello all,
> >
> > The "backupcopy" option does not appear to be working as
> > documented in the version of VIM I have built locally. As the
> > run-time contains online help for the feature I
On Fri, Oct 25, 2019 at 4:05 AM Sihera Andre
wrote:
>
> Tony,
> Christian,
> Sorry for the delayed response.
>
> On 24/10/2019 11:07, Tony Mechelynck wrote:
> >
> > Runtime files ought to be of a version as close as possible to the
> > executable with which th
On Thu, Oct 24, 2019 at 3:21 AM Sihera Andre wrote:
>
> Hello all,
>
> Apologies for posting to the mailing list before filing a bug report
> but I just wanted to make sure that I was facing a bug and not a silly
> build error of some kind.
Bug reports come to the mailing list anyway, so no
On Fri, Oct 18, 2019 at 8:58 AM Jay Thompson wrote:
>
> I saw a tweet recently with a screenshot of the MS Word 5.1 splash screen:
> https://twitter.com/hondanhon/status/1183601276010893312
>
> The logo looks familiar. Is the vim logo a deliberate reference to this logo?
Hm, this tweet seems to
On Sun, Oct 13, 2019 at 12:37 PM Shidong Wang wrote:
>
> Hello, I just want to build the vim on my old linux system. but I get
> following error. I have searched in google, but failed.
>
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_ATHENA -I/usr/local/include
> -O -o
On Fri, Oct 11, 2019 at 1:37 PM Shidong Wang wrote:
>
> Hello, I have lua command in my vimrc, but when start gvim, I got E370 failed
> to load lua53.dll, but all my lua code are surrounded by try catch. (emty
> srting after catch).
> --
> wsdjeg
Instead of catching E370 after it
On Sun, Oct 6, 2019 at 12:15 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > On Sat, Oct 5, 2019 at 11:57 AM Bram Moolenaar wrote:
> > >
> > >
> > > Patch 8.1.2113
> > > Problem:":help expr-!~?" only works after searching.
> > > Solution: Escape "~" after "expr-". (closes #5015)
> > >
On Sat, Oct 5, 2019 at 11:57 AM Bram Moolenaar wrote:
>
>
> Patch 8.1.2113
> Problem:":help expr-!~?" only works after searching.
> Solution: Escape "~" after "expr-". (closes #5015)
> Files: src/ex_cmds.c, src/testdir/test_help.vim
Strangely enough, in Vim 8.1.2117 (with GTK2 GUI on
On Sun, Sep 29, 2019 at 8:35 PM Yegappan Lakshmanan wrote:
>
> Hi Tony,
>
> On Sun, Sep 29, 2019 at 10:22 AM Tony Mechelynck
> wrote:
> >
> > On Sun, Sep 29, 2019 at 7:03 PM Bram Moolenaar wrote:
> > > Patch 8.1.2101
> > > Problem:wr
On Sun, Sep 29, 2019 at 7:03 PM Bram Moolenaar wrote:
> Patch 8.1.2101
> Problem:write_session_file() often defined but not used.
> Solution: Adjust the #ifdef. (Yegappan Lakshmanan, closes #4998)
> Files: src/session.c
Link error in Huge build (only):
gui_gtk_x11.c:(.text+0x1062):
Compile error in Normal and Big (but not in Tiny, Small and Huge)
after applying patches 8.1 2074-2076
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
On Wed, Sep 18, 2019 at 1:46 PM Christian Brabandt wrote:
>
>
> On Mi, 18 Sep 2019, Bram Moolenaar wrote:
>
> > Let's be practical: We fixed something because a user complained and it
> > was clear it had to be fixed. For "x" deleting a line we did not get
> > complaints. And, depending on how
no spaces.
Best regards,
Tony.
On Sun, Sep 15, 2019 at 9:47 AM Tony Mechelynck
wrote:
>
> On Sun, Sep 15, 2019 at 8:55 AM Shidong Wang wrote:
> >
> > Hello, I am not sure if it is a bug, but it always make me confuses:
> >
> > here is a exmaple:
> >
>
On Sun, Sep 15, 2019 at 8:55 AM Shidong Wang wrote:
>
> Hello, I am not sure if it is a bug, but it always make me confuses:
>
> here is a exmaple:
>
> func Test()
> let c = 'sss'
> let a = 1
> let b = 2
> echo c[a:b]
> endf
>
> then call Test(), you will get error, Undefined variable:
On Sat, Sep 14, 2019 at 10:51 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > Build error in screen.c in Tiny and Small after applying patches
> > 8.1.2028 to 8.1.2031. No change after 8.1.2032.
> >
> > screen.c: In function ‘win_line’:
> > screen.c:5386:10: error: ‘line_attr’ undeclared (first
Build error in screen.c in Tiny and Small after applying patches
8.1.2028 to 8.1.2031. No change after 8.1.2032.
screen.c: In function ‘win_line’:
screen.c:5386:10: error: ‘line_attr’ undeclared (first use in this
function); did you mean ‘win_attr’?
if (line_attr)
^
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
-D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o
objects/arabic.o arabic.c
In file included from
On Mon, Sep 2, 2019 at 11:16 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > I just noticed that hitting : without a command name is a valid
> > ex-command which does nothing (other than going to a range if there is
> > one). I propose to document it, see attached patch.
> >
> > The range (if
I just noticed that hitting : without a command name is a valid
ex-command which does nothing (other than going to a range if there is
one). I propose to document it, see attached patch.
The range (if present) can IIUC be any valid range, not just an
absolute line number but also e.g. a relative
On Sat, Aug 31, 2019 at 3:29 PM Bram Moolenaar wrote:
>
>
> Tony Wrote:
>
> > I'm attaching a proposed patch. I wrote the recipe as "@test -e ./$@
> > || ln -sv ../$@" rather than just the ln command to make 100% sure it
> > doesn't try to recreate an existing link. AFAICT it works for me. I
> >
I'm attaching a proposed patch. I wrote the recipe as "@test -e ./$@
|| ln -sv ../$@" rather than just the ln command to make 100% sure it
doesn't try to recreate an existing link. AFAICT it works for me. I
don't know why it rebuilds auto/pathdef.c, objects/pathdef.o and
objects/version.o even
On Fri, Aug 30, 2019 at 2:00 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1942
> Problem:Shadow directory gets outdated when files are added.
> Solution: Add the "shadowupdate" target and add a few comments.
> Files: src/Makefile
>
>
> *** ../vim-8.1.1941/src/Makefile2019-08-27
On Thu, Aug 29, 2019 at 8:59 PM Bram Moolenaar wrote:
>
>
> Christian wrote:
>
> > On Mi, 28 Aug 2019, Bram Moolenaar wrote:
> >
> > >
> > > > Recently you've been proposing (and Bram has accepted) to create a lot
> > > > of new source files to make the existing source easier to understand.
> > >
201 - 300 din 2203 matches
Mail list logo
