On Wed, Aug 28, 2019 at 10:54 PM Tony Mechelynck
wrote:
>
> On Wed, Aug 28, 2019 at 5:37 PM Yegappan Lakshmanan
> wrote:
> > Are you trying to update an existing shadow directory? Are the
> > symbolic links to the new .c files created if you clean the view and run
&g
On Wed, Aug 28, 2019 at 10:19 PM 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.
> > The notion is laudable but it doesn't work well with my shadow
> > directories: every
On Wed, Aug 28, 2019 at 5:37 PM Yegappan Lakshmanan wrote:
>
> Hi Tony,
>
> On Tue, Aug 27, 2019 at 11:17 PM Tony Mechelynck
> wrote:
> >
> > Dear Yegappan,
> >
> > Recently you've been proposing (and Bram has accepted) to create a lot
> > of new so
Dear Yegappan,
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.
The notion is laudable but it doesn't work well with my shadow
directories: every time there is a new .c source (or .h; .pro sources
are
On Fri, Aug 23, 2019 at 8:35 PM Bram Moolenaar wrote:
> Thanks, I updated https://www.vim.org/mercurial.php
> We'll update it again when we get feedback about which one works best.
I'm not sure there's a single one which works *best*, i.e. definitely
better than both others at the moment. AFAIK,
On Fri, Aug 23, 2019 at 8:40 AM Christian Brabandt wrote:
>
>
> On Do, 22 Aug 2019, Bram Moolenaar wrote:
>
> > What are the "hg clone" commands to use? For bitbucket it's:
> >
> > hg clone https://bitbucket.org/vim-mirror/vim
>
> hg clone http://hg.256bit.org/vim or
> hg clone
On Tue, Aug 20, 2019 at 3:51 PM 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
Full details:
https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
2020-02-01 and on 2020-06-01 all existing Mercurial repos on bitbucket
will be deleted. From then on it will only support git repos.
How it
On Tue, Aug 20, 2019 at 1:01 PM Zdenek Dohnal wrote:
>
> Hi all,
>
> I found out there is Vimx symlink to gvim binary in my Vim package in Fedora.
>
> Does anyone know what Vimx is/was? What behavior did it have?
>
> I see from man page:
>
> vimx Starts gvim in "Vi" mode similar to "vim",
On Mon, Aug 19, 2019 at 8:04 PM Tony Mechelynck
wrote:
> That's it!
> src/shadow-big/arglist.c should be a link to ../arglist.c, but it is a
> text file instead, and there get_arglist_name is breacketed between
> "#if defined(FEAT_CMDL_COMPL) || defined(PROTO)" .. "#en
On Mon, Aug 19, 2019 at 3:25 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > > > 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
On Mon, Aug 19, 2019 at 1:55 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > 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
> >
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/cmdexpand.o
objects/cmdhist.o
On Tue, Aug 6, 2019 at 3:32 PM Alexis Reynouard
wrote:
>
> Hello,
>
> I tried to write syntax and indent files (attachment) for .brf files,
> http://brouter.de/brouter/costfunctions.html
>
>
> It is the first time I do something with vim more than simple usage, so
> probably it needs some fixes.
On Sun, Aug 4, 2019 at 3:04 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1807
> Problem:More functions can be used as a method.
> Solution: Add append(), appendbufline(), assert_equal(), etc.
> Also add the :eval command.
> Files: runtime/doc/eval.txt, runtime/doc/testing.txt,
On Sat, Aug 3, 2019 at 2:24 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1797 (after 8.1.1794)
> Problem:The vgetorpeek() function is too long.
> Solution: Split off the part that handles mappings, with fix.
> Files: src/getchar.c
After applying this fix, I get the following warning in
After applying patches 1738 to 1746 (of release 8.1) I get the
following warnings (in Tiny and Small only). An executable is
produced. I suspect patch 8.1.1744.
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o
On Sun, Jul 14, 2019 at 2:56 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > "profiling.c" and "profiling.pro" should be "profiler.c" and
> > "profiler.pro" respectively.
>
> I'll correct that in the text.
>
> > If (like me) you're compiling in a shadow
> > directory, you must link profiler.c,
"profiling.c" and "profiling.pro" should be "profiler.c" and
"profiler.pro" respectively. If (like me) you're compiling in a shadow
directory, you must link profiler.c, not profiling.c, from the
shadowdir to its parent, i.e. (the shadow directory being current, and
assuming a Unix-like OS)
On Fri, Jul 12, 2019 at 5:56 AM Daan van Rossum wrote:
>
> Dear vim devs,
>
> There is one seemingly simple feature that is missing in vim, so I though it
> is time to bring it up:
>
> Feature: simple action (dot-key) history table.
>
> Quoting vim help:
> ```
> There are actually five history
On Thu, Jul 11, 2019 at 9:55 AM Paul Jolly wrote:
>
> Hi all,
>
> I've tried various permutations of search terms, but so far turned up a blank.
>
> Is there a function/similar that will allow me to set buffer contents
> between a start and end byte offset?
>
> If there isn't, I have a "backup"
On Sun, Jul 7, 2019 at 11:10 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > Compiler warnings in Normal and Big after applying patches 1648 and 1649.
> >
> > No warnings in Huge, Small or Tiny.
> >
> > I'm attaching my configure settings.
>
> I tried a similar config, didn't see any warnings.
>
Compiler warnings in Normal and Big after applying patches 1648 and 1649.
No warnings in Huge, Small or Tiny.
I'm attaching my configure settings.
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
On Wed, Jun 26, 2019 at 3:41 AM Bram Moolenaar wrote:
>
>
> Patch 8.1.1597
> Problem:Cannot scroll a popup window with the mouse.
> Solution: If the popup window has a scrollbar let the mouse scroll wheel
> scroll the window.
> Files: runtime/doc/popup.txt, src/normal.c,
On Wed, Jun 26, 2019 at 1:06 AM Bram Moolenaar wrote:
>
>
> Patch 8.1.1596
> Problem:When resizing the screen may draw popup in wrong position. (Masato
> Nishihata)
> Solution: Check the popup is not outside of the screen. (fixes #4592)
> Files: src/popupwin.c
Warning in
On Thu, Jun 20, 2019 at 3:46 AM Bram Moolenaar wrote:
> Should be fixed by 8.1.1572
Yes, it was. Thanks Bram!
--
--
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
No warnings in Normal and bigger.
I suspect this might be a result of the #ifdef move in patch 8.1.1569.
For example in Tiny:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o
objects/screen.o screen.c
screen.c: In
* 4 warnings "variable set but not used" in Tiny and Small option.c
after applying patches 1537 to 1551. Maybe a missing #ifdef ?
* No warning in Normal or higher.
Example for Tiny:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce
-Wall -D_REENTRANT -U_FORTIFY_SOURCE
Whenever a new source file gets added, all my builds suddenly fail (I
don't use -j but I build different featuresets in parallel, each in
its own shadow directory). They fail of course with the message "No
rule to make" for the new file. (It happeneed recently for sound.c.)
The solution isn't
On Thu, Jun 6, 2019 at 7:47 PM Christian Brabandt wrote:
[...]
> --
> Unordnung: wo nichts am rechten Platz ist.
> Ordnung: wo am rechten Platz nicht ist.
The following is the start of a chapter from "Citadel" by Antoine de
Saint-Exupéry (my translation, and quoting from memory):
My generals,
On Sun, Jun 2, 2019 at 9:02 PM Gary Johnson wrote:
>
> On 2019-06-02, tooth pik wrote:
>
> > what's a full stop again?
>
> Full stop is the term in British English for what is a period in
> American English. It is the last character in these sentences.
>
> Regards,
> Gary
BTW, the official
On Sun, Jun 2, 2019 at 8:08 PM tooth pik wrote:
> what's a full stop again?
the little dot you write at the end of a sentence, to create a long
pause — longer than for a semicolon, which is longer than for a comma.
You know what a comma is, don't you? Well, a semicolon is a dot above
a comma.
iscussion on the web visit
https://groups.google.com/d/msgid/vim_dev/CAJkCKXvtG_EZ2HeuMcz8k8SqXSXmedSijG_%3D3gjKoVJ9PKFM5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
# HG changeset patch
# User Tony Mechelynck
# Parent 51928ea81f7fbd9cb9bcd269067bf2b1faf92d
On Sun, May 26, 2019 at 1:14 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > See below the error (at src/Makefile line 2009) as displayed in the
> > Tiny build without GUI but with +xterm_save. Small with Motif GUI
> > gives the same error. No error in Normal, Big and Huge with GTK2 GUI.
> >
See below the error (at src/Makefile line 2009) as displayed in the
Tiny build without GUI but with +xterm_save. Small with Motif GUI
gives the same error. No error in Normal, Big and Huge with GTK2 GUI.
link.sh: $LINK_AS_NEEDED set to 'yes': invoking linker directly.
gcc -L/usr/local/lib
On Tue, May 21, 2019 at 2:31 PM Jason Franklin
wrote:
>
> > Does this also fix https://github.com/vim/vim/issues/4352 I suppose not?
>
> No, it does not fix that issue.
>
> However, I'm not exactly sure that the issue referenced is a valid
> complaint. It was my understanding that buffer numbers
On Mon, May 20, 2019 at 1:31 PM Antony Scriven wrote:
>
> Hi!
>
> > Solution: Only use the "extends" character when 'list' is on. (Hirohito
> > Higashi, closes #4360)
>
> This change may be consistent, but is it helpful?
>
> It seems to me that extends and precedes provide basic
On Wed, May 15, 2019 at 11:40 PM Vedanth Srinivasan wrote:
>
> Is there any way I can get a local history for a file in vim? I have already
> completed the file and am trying to see my changes at each point.
This is more of a question for vim_use than for vim_dev.
See
:help u
On Sat, May 11, 2019 at 2:34 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1317
> Problem:Output from Travis can be improved.
> Solution: Add section headers. Handle errors better. (closes #4098)
> Files: .travis.yml, configure
The if_ver-1.vim and if_ver2.vim scripts used in (the
On Thu, May 9, 2019 at 7:22 PM tooth pik wrote:
>
> i get a weird error when i try to git pull this patch
>
> Updating eae1b91fe..a6c27c47d
> error: Your local changes to the following files would be overwritten by
> merge:
> runtime/gvim.desktop
> runtime/vim.desktop
> Please
Currently with 'incsearch' and 'hlsearch' both on, when searching for
a pattern including \Z (i.e. disregard composing characters) with (if
it makes a difference) the old search engine (i.e. 'regexpengine' set
to 1) this is what I observe:
- 'hlsearch' highlighting is correct (in gvim with default
On Wed, May 1, 2019 at 6:09 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1241
> Problem:Ex command info contains confusing information.
> Solution: When using the NOTADR flag use ADDR_OTHER for the address type.
> Cleanup code using NOTADR. Check for errors in
>
On Wed, May 1, 2019 at 7:29 PM brad summerquist
wrote:
>
> I'm using gvim 8.1.1 on windows 10 without a profile ("gvim -u NONE").
>
> I'm running the ":sort" command on the following lines:
>
> a
> z
> B
> b
>
> :sort is giving me this =>
>
> B
> a
> b
> z
>
> I'd expect the lowercase 'a' to be
On Wed, May 1, 2019 at 1:16 PM Tony Mechelynck
wrote:
>
> According to the help, 'cmdheight' is global. However, :tabnew followed by
> setlocal ch=3 changes it only for the new tab; but by going back to the
> previous tab and returning to the new tab, setl ch? answers
On Tue, Apr 30, 2019 at 9:27 PM Bram Moolenaar wrote:
> During build the generated vim.desktop and gvim.desktop are copied to
> the runtime directory. That's not a good idea. But we need those files
> for "make install". Let's adjust the "make install" commands to use the
> po/*.desktop files
On Tue, Apr 30, 2019 at 9:28 PM Bram Moolenaar wrote:
>
> Patch 8.1.1240
> Problem:Runtime desktop files are overwritten by build. (Tony Mechelynck)
> Solution: Instead of copying the files find them with "make install".
> Files: src/Makefile, src/po/M
On Mon, Apr 29, 2019 at 8:31 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > 1. hg --verbose clone https://bitbucket.org/vim-mirror/vim vim-hg
> > 2. cd vim-hg/src
> > 3. make distclean # IMPORTANT! otherwise "make shadow" will run
> > configure first)
> > 4. SHADOWDIR=shadow-huge make -e
P.S. I tried popping the changes into an mq patch. Strangely enough,
AFAICT the changes done by "make" in the desktop files seem to consist
in the _removal_ of the German localizations (see attachment).
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not
1. hg --verbose clone https://bitbucket.org/vim-mirror/vim vim-hg
2. cd vim-hg/src
3. make distclean # IMPORTANT! otherwise "make shadow" will run
configure first)
4. SHADOWDIR=shadow-huge make -e shadow
5. cd shadow-huge
6. ln -svf ../Makefile
7. ln -sv ../../../hugecfg myconfig # preset
On Sun, Apr 28, 2019 at 3:00 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1225
> Problem:Cannot create a pty to use with :terminal on FreeBSD.
> Solution: Add support for posix_openpt(). (Ozaki Kiichi, closes #4306,
> closes #4289)
> Files: src/configure.ac, src/config.h.in,
Looking at the help for the 'tagcase' option today, I was surprised to see both
{not in Vi}
and
NOTE: This option is set to the Vi default value when 'compatible' is
set and to the Vim default value when 'compatible' is reset.
This looks confusing to me (and I suspect that other
On Tue, Apr 23, 2019 at 11:48 AM Dominique Pellé
wrote:
>
> Christian Brabandt wrote:
>
> > On Di, 23 Apr 2019, tooth pik wrote:
> >
> > > is "make test" supposed to work currently? i can't remember the last
> > > time i didn't
> > > get a failed somethingorother from it
> > >
> > > this time
On Tue, Apr 16, 2019 at 10:21 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1177
> Problem:.ts files are recognized as xml, while typescript is more common.
> Solution: Recognize .ts files as typescript. (closes #4264)
> Files: runtime/filetype.vim src/testdir/test_filetype.vim
Alas, the
On Thu, Apr 11, 2019 at 8:15 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > On Thu, Apr 11, 2019 at 6:45 PM Bram Moolenaar wrote:
> > >
> > >
> > > Patch 8.1.1153
> > > Problem: Msgfmt complains about missing LINGUAS file. (Tony Mechely
On Thu, Apr 11, 2019 at 6:45 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1153
> Problem:Msgfmt complains about missing LINGUAS file. (Tony Mechelynck)
> Solution: Add command to generate LINGUAS.
> Files: src/po/Makefile
For some reason I don't see this changeset on th
On Thu, Apr 11, 2019 at 5:57 PM Tony Mechelynck
wrote:
>
> I get the following messages at the end of "make" after soft-linking
> ../../po/vim.desktop.in and ../../po/gvim.desktop.in from the po
> subdirectory in each one of my shadow directories.
P.S. Package gettext-r
I get the following messages at the end of "make" after soft-linking
../../po/vim.desktop.in and ../../po/gvim.desktop.in from the po
subdirectory in each one of my shadow directories. These messages are
probably due to running incremental make in shadow directories (rather
than deleting and
On Wed, Apr 10, 2019 at 10:34 PM Bram Moolenaar wrote:
> Patch 8.1.1144 (after 8.1.1143)
> Problem:Too strict checking of the 'spellfile' option.
> Solution: Allow for a path.
> Files: src/option.c, src/testdir/test_spell.vim
Warning in Tiny and Small; gcc proceeds to link phase.
gcc
On Sun, Apr 7, 2019 at 1:26 PM Tony Mechelynck
wrote:
>
> On Sun, Apr 7, 2019 at 12:05 PM Bram Moolenaar wrote:
> >
> >
> > Patch 8.1.1134
> > Problem:Buffer for quickfix window is reused for another file.
> > Solution: Don't reuse the quickfx buf
On Sun, Apr 7, 2019 at 12:05 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1134
> Problem:Buffer for quickfix window is reused for another file.
> Solution: Don't reuse the quickfx buffer. (Yegappan Lakshmanan)
> Files: src/buffer.c, src/testdir/test_quickfix.vim
Link error in Tiny and
On Sun, Apr 7, 2019 at 5:10 AM Yegappan Lakshmanan wrote:
>
> Hi,
>
> I see that an empty quickfix buffer is reused for loading a normal
> file. The following steps illustrate the problem:
>
> $ vim
> :copen
> :only
> :edit normal.c
> :cexpr "Test"
>
> Now the quickfix
On Thu, Apr 4, 2019 at 3:36 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1114
> Problem:Confusing overloaded operator "." for string concatenation.
> Solution: Add ".." for string concatenation. Also "let a ..= b".
> Files: src/eval.c, src/testdir/test_eval_stuff.vim, runtime/doc/eval.txt
Warning in arabic.c at patchlevel 8.1.1076 in Huge and Big builds only
For instance in Big build:
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 Sat, Mar 23, 2019 at 1:00 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > On Fri, Mar 22, 2019 at 5:03 PM Bram Moolenaar wrote:
> > I suppose it could still be enabled by editing src/feature.h but that
> > was of little use anyhow.
>
> Yes, enabling a feature by recompiling isn't useful.
On Fri, Mar 22, 2019 at 5:03 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.1040
> Problem:FEAT_TAG_ANYWHITE is not enabled in any build.
> Solution: Remove the feature.
> Files: src/feature.h, src/tag.c, src/evalfunc.c, src/version.c,
> src/Make_vms.mms
I suppose it could still
There is a reason for these two forms. The older one (without "set")
is vi-compatible (at least when prefixed by "vi:" or "ex:" rather than
"vim:"): for instance the modeline for the help.txt helpfile:
vim:tw=78:isk=!-~,^*,^\|,^\":ts=8:noet:ft=help:norl:
As you can see, here colons separate
On Sat, Mar 9, 2019 at 10:42 PM Dominique Pellé
wrote:
>
> Tony Mechelynck wrote:
>
> > On Sat, Mar 9, 2019 at 9:15 PM Dominique Pellé
> > wrote:
> > >
> > > Hi
> > >
> > > Attached patch fixes capitalization of vim functions
&g
On Sat, Mar 9, 2019 at 9:15 PM Dominique Pellé
wrote:
>
> Hi
>
> Attached patch fixes capitalization of vim functions
> in documentation.
>
> Regards
> Dominique
Looks like there was a conflict between either writing the first word
of a sentence with an initial capital letter, or not altering
On Fri, Mar 8, 2019 at 1:14 PM Jón Arnar Briem wrote:
>
> Thank you both for your responses, we had originally thought of adding
> translations since we speak some languages which are lacking support but your
> suggestions of adding to the test coverage are also interesting. As for the
>
After applying patches (8.1.) 953 to 956 I get the following warning
in Tiny and Small builds (only):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/ex_cmds.o
ex_cmds.c
ex_cmds.c: In function ‘ex_sort’:
On Tue, Feb 19, 2019 at 7:35 AM Christian Brabandt wrote:
>
>
> On Mo, 18 Feb 2019, Jason Franklin wrote:
>
> > Greetings,
> >
> > Trying to figure out if this is intentional or not. It is definitelya
> > backward search?
> > surprising given how the documentation (":h gn") is written.
> >
> >
On Thu, Feb 7, 2019 at 8:21 AM Gary Johnson wrote:
>
> On 2019-02-06, Tony Mechelynck wrote:
> > No one says that politicians should design institutions tailored to the
> > house in which I live.
> >
> > AFAICT, the above post is off-topic, and so is the f
On Mon, Feb 4, 2019 at 9:36 PM Christian Brabandt wrote:
>
>
> On Mo, 04 Feb 2019, Bram Moolenaar wrote:
>
> > Now that is weird. I'm sure I added the file, but somehow it
> > disappeared again. Looks like this happened because the directory is
> > new, but it didn't give me an error. Try
On Sun, Feb 3, 2019 at 11:47 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0873
> Problem:List if distributed files does not include the matchit autoload
> directory.
> Solution: Add the directory.
> Files: src/Filelist
After applying this patch then running "make install", the
On Sun, Feb 3, 2019 at 4:17 PM Christian Brabandt
wrote:
>
> Bram, the autoload script for matchit is missing.
I confirm the problem. Hitting % in Normal mode gives:
not found in 'runtimepath': "autoload/matchit.vim"
E117: Unknown function: matchit#Match_wrapper
Best regards,
Tony.
--
--
P.S. Link does _not_ proceed to completion:
gcc -L/usr/local/lib -Wl,--as-needed-o vi objects/arabic.o
objects/autocmd.o objects/beval.o objects/buffer.o objects/blob.o
objects/blowfish.o objects/crypt.o objects/crypt_zip.o objects/dict.o
objects/diff.o objects/digraph.o
On Thu, Jan 31, 2019 at 1:48 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0857
> Problem:Ignore functionality is not separated.
> Solution: Move indent functionality into a new file. (Yegappan Lakshmanan,
> closes #3886)
> Files: Filelist, src/Make_bc5.mak,
On Thu, Jan 24, 2019 at 1:39 AM Bram Moolenaar wrote:
>
>
> Tony Mechelynck wrote:
>
> > On Wed, Jan 23, 2019 at 8:30 PM Bram Moolenaar wrote:
> > > I think what we can do is to keep the "#ifdef EBCDIC" lines and just
> > > remove the "#ifdef FE
On Wed, Jan 23, 2019 at 8:30 PM Bram Moolenaar wrote:
> I think what we can do is to keep the "#ifdef EBCDIC" lines and just
> remove the "#ifdef FEAT_MBYTE" conditions. Then, when 'encoding' is set
> to "latin1" and Vim is build with EBCDIC defined, hopefully it will just
> work. Well, there
On Mon, Jan 21, 2019 at 9:30 PM Kevin Bulgrien wrote:
>
> > It seems unfortunate for gvim's ex man page not to document use of the
> > vertical bar delimiter in lieu of multiple -c arguments since it does
> > mention that not all implementations support use of multiple -c
> > arguments.
>
>
On Mon, Jan 21, 2019 at 4:59 PM Bram Moolenaar wrote:
> 788 fixes this. I assumed the code was mostly OK, but it wasn't, the
> #ifdefs were misplaced. Thus it needed some more changes.
Yeah, I saw the new patch after I sent the problem report. Thanks.
Best regards,
Tony.
--
--
You received
On Sun, Jan 20, 2019 at 6:40 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0787
> Problem:Compiler warning for unused function. (Tony Mechelynck)
> Solution: Tune #ifdef around setjmp functions.
> Files: src/os_unix.c
Before this change, os_unix.c compiled, albeit wit
On Sun, Jan 20, 2019 at 3:31 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0785
> Problem:Depending on the configuration some functions are unused.
> Solution: Add more #ifdefs, remove unused functions. (Dominique Pelle,
> closes #3822)
> Files: src/buffer.c, src/channel.c,
On Sat, Jan 19, 2019 at 2:56 PM Dominique Pellé
wrote:
>
> Hi
>
> Attached patch fixes 2 typos in the doc.
>
> Dominique
In the second one, "to not call" should be "not to call" which is the
correct negative form of the English infinitive.
Best regards,
Tony.
--
--
You received this message
I propose the attached patch to runtime/doc/eval.txt to document the
dots in blob literals and in the output of string(blob)
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 Tue, Jan 15, 2019 at 10:52 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0757
> Problem:Not enough documentation for Blobs.
> Solution: Add a section about Blobs.
> Files: runtime/doc/eval.txt
Ah, this is much better.
I suppose the item at todo.txt lines 142-143 can now be removed.
I
On Mon, Jan 14, 2019 at 8:17 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0745
> Problem:Compiler warnings for signed/unsigned string.
> Solution: Remove type casts. (John Marriott)
> Files: src/ex_docmd.c, src/mbyte.c
After this patch, there is one signedness warning in Small and Tiny
On Sat, Jan 12, 2019 at 1:26 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0729
> Problem:There is a SourcePre autocommand event but not a SourcePost.
> Solution: Add the SourcePost autocommand event. (closes #3739)
> Files: src/vim.h, src/fileio.c, src/ex_cmds2.c, runtime/doc/autocmd.txt,
On Fri, Jan 11, 2019 at 4:37 PM Dominique Pellé
wrote:
>
> Bram Moolenaar wrote:
>
> > Currently it's still possible to build Vim without multi-byte support.
> > This leads to a large number of #ifdefs. And is a text editor without
> > multi-byte support still useful these days?
> >
> > The
The present "xim-input-style" help paragraph seems to me difficult to
understand. I've tried to rewrite it to make it more understandable
while keeping the exact same meaning, see the proposed diff attached
to this mail.
As I am no XIM specialist, I don't know if this help section is
up-to-date
On Sun, Jan 6, 2019 at 3:30 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0696
> Problem:When test_edit fails 'insertmode' may not be reset and the next
> test may get stuck. (James McCoy)
> Solution: Always reset 'insertmode' after executing a test. Avoid that an
>
On Sat, Dec 29, 2018 at 6:55 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0658
> Problem:Deleting signs and completion for :sign is insufficient.
> Solution: Add deleting signs in a specified or any group from the current
> cursor location. Add group and priority to sign command
>
On Sat, Dec 22, 2018 at 5:29 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0624 (after 8.2.0620)
> Problem:Overuling CONF_ARGS from the environment still does not work.
> (Tony
> Mechelynck)
> Solution: Add back CONF_ARGS next to the new numbered ones.
>
My previous post was before looking at patch 8.1.0620. I see that the
line was not commented-out but removed, and that $(CONF_ARGS) was
replaced in the arguments of auto/configure by the concatenation of
the six $(CONF_ARGS1) to $(CONF_ARGS6) which moves forward rather than
backwards. This way my
On Sat, Dec 22, 2018 at 2:54 PM Bram Moolenaar wrote:
>
>
> Gary Johnson wrote:
>
> > On 2018-12-22, Tony Mechelynck wrote:
> > > Setting $CONF_ARGS in the environment doesn't work anymore: it is
> > > overridden (unless make is called with the -e switch
Setting $CONF_ARGS in the environment doesn't work anymore: it is
overridden (unless make is called with the -e switch, which is not
normal practice) by the line
CONF_ARGS = $(CONF_ARGS1) $(CONF_ARGS2) $(CONF_ARGS3) $(CONF_ARGS4)
$(CONF_ARGS5)
at line 326 of src/Makefile. Setting $CONF_ARGS1 to
I notice that the cursor behaviour depends on the 'list' setting. With
'list' on (and something for "tab:" in 'listchars', I use "tab:|_"
i.e. ":set lcs=eol:¶,tab:\|_,extends:>,precedes:<,conceal:*,nbsp:·"
after setting 'encoding' to utf-8 if it doesn't yet start with u or U)
when the cursor is on
On Sun, Dec 16, 2018 at 2:26 AM Tony Mechelynck
wrote:
>
> On Sun, Dec 16, 2018 at 1:59 AM Yegappan Lakshmanan
> wrote:
> >
> > Hi all,
> >
> > I am seeing that the cursor is displayed at an incorrect column
> > if I do the following (using the latest v
On Sun, Dec 16, 2018 at 1:59 AM Yegappan Lakshmanan wrote:
>
> Hi all,
>
> I am seeing that the cursor is displayed at an incorrect column
> if I do the following (using the latest version of Vim on Mac):
>
> 1. Add an empty line to a buffer with a tab character followed by
> a space at the
On Thu, Dec 13, 2018 at 10:21 PM Bram Moolenaar wrote:
>
>
> Patch 8.1.0580
Note: This is actually patch 8.1.0579, and marked as such in version.c
> Problem:Cannot attach properties to text.
> Solution: First part of adding text properties.
>From doc/textprop.txt:
> Text properties can
301 - 400 din 2203 matches
Mail list logo
