BTW, I'm sorry if this has been asked before as I didn't have time to
catch all my emails recently, but if the vartab feature is to be used
for column editing (and it's great at that), wouldn't it be more
logical to provide the columns where to stop at rather than the length
of tabs?
For
Hello,
:h varsofttabstop reads :
For example, when editing assembly language files where statements
start in the 8th column and comments in the 40th, it may be useful
to use the following:
:set varsofttabstop=8,32,8
To me, this will move the cursor to the 9th (inserting 8 spaces) and
41th
On Thu, Jun 28, 2018 at 11:34 PM, tux. wrote:
> As some of you might know, I provide my own Windows Vim builds. My
> latest hardware upgrade brought a new infrastructure though.
>
> I usually compile six Vims in a row:
>
> - x86 GVim without OLE
> - x86 GVim with OLE
> - x86 CLI Vim
> - the same
As some of you might know, I provide my own Windows Vim builds. My
latest hardware upgrade brought a new infrastructure though.
I usually compile six Vims in a row:
- x86 GVim without OLE
- x86 GVim with OLE
- x86 CLI Vim
- the same for amd64
Now I get these errors _exclusively_ with x86 GVim
Well, very few people are still using 8.3 systems.
So, that is no longer a problem, but it explains the choice
to go with three letter suffixes. Even today, most of the
Vim documentation (e.g. doc/options.txt) uses 8.3 names.
And yes, newer documentation is not limited to 8.3 character
names (e.g.
Patch 8.1.0126
Problem:Various problems with 'vartabstop'.
Solution: Fix memory leak. Fix crash. Add a few more tests. (Christian
Brabandt, closes #3076)
Files: src/ex_cmds.c, src/option.c, src/screen.c,
src/testdir/test_vartabs.vim
***
Den 28-06-2018 kl. 21:39 skrev Antonio Giovanni Colombo:
I think the reason was to use two letters to identifiy the language, and
keep the third one fixed ("x") because in the old day of MS-DOS 8.3
names, the suffixes were usually of three letters. I have no problem at
all with this. All boils
I think the reason was to use two letters to identifiy the language, and
keep the third one fixed ("x") because in the old day of MS-DOS 8.3 names,
the suffixes were usually of three letters. I have no problem at all with
this. All boils down to "easy to manage".
On Thu, Jun 28, 2018 at 8:45 PM
Den 28-06-2018 kl. 20:14 skrev Antonio Giovanni Colombo:
Hi,
the reason for the suffix in the file names is that "that way" all the
files (and the tags tags-ll files) are in the same directory. That makes
a lot of sense to me (I don't have to define a directory to get the
Italian docs, and
Hi,
the reason for the suffix in the file names is that "that way" all the
files (and the tags tags-ll files) are in the same directory. That makes a
lot of sense to me (I don't have to define a directory to get the Italian
docs, and the English docs are always available asking e.g. intro@en).
Patch 8.1.0125
Problem:Virtual edit replace with multi-byte fails at end of line. (Lukas
Werling)
Solution: use ins_char() to add the character. (Christian Brabandt,
closes #3114) Rename PCHAR() to PBYTE() to avoid mistakes like
this.
Files:
It seems the translation files are using three different "systems".
If i translate to "da" its:
lang/da/LC_MESSAGES/vim.mo (da is folder)
lang/menu_da.utf-8.vim (da is part of filename)
doc/intro.dax (da is part of filename extension)
The last one seems strange to change the extension.
I would
We can assume users will only get one of the packages and know where to
find it. Putting them in a central place doesn't really help for that.
It would have helped the users looking for french, persian or polish
translations because the links on https://www.vim.org/translations.php
dont
Shouldn't the translated help files be (like the translated menu and
messages files already are) part of Vim's version control system, i.e.
shouldn't they live somewhere on Vim's git server (and therefore on
its Mercurial mirror)? Then "make installruntime" (and therefore "make
install") would
Den 28-06-2018 kl. 15:39 skrev Antonio Giovanni Colombo:
> > Are there something simalar for the help translations?
> > Like maybe ":set helplang=da something" could download the danish help
> > files.
> >
> We currently don't do that, but I suppose it's possible. We would need
> to have
Patch 8.1.0124
Problem:has('vcon') returns true even for non-win32 terminal.
Solution: Check the terminal type. (Nobuhiro Takasaki, closes #3106)
Files: src/evalfunc.c
*** ../vim-8.1.0123/src/evalfunc.c 2018-06-24 19:01:55.411752372 +0200
--- src/evalfunc.c 2018-06-28
> > Are there something simalar for the help translations?
> > Like maybe ":set helplang=da something" could download the danish help
> > files.
> >
> We currently don't do that, but I suppose it's possible. We would need
> to have the mapping from language to download location in the
>
Patch 8.1.0123
Problem:MS-Windows: colors are wrong after setting 'notgc'.
Solution: Only call control_console_color_rgb() for the win32 terminal.
(Nobuhiro Takasaki, closes #3107)
Files: src/option.c
*** ../vim-8.1.0122/src/option.c2018-06-24 23:53:25.153526495
I see now. Thanks for the explanation!
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the
Jason Franklin wrote:
> I was a little confused by this patch, and I was hoping you'd enlighten me.
>
> 1. I see that the error messages from the test don't show up when I restored
> 'modifiable' in the original patch. So I didn't see them while working.
>
> 2. They also go away when using
Patch 8.1.0122
Problem:Translators don't always understand the maintainer message.
Solution: Add a comment that ends up in the generated po file. (Christian
Brabandt, closes #3037)
Files: src/message.c
*** ../vim-8.1.0121/src/message.c 2018-06-23 19:22:45.610486284
> I dont know much about Vim but i saw running ":set spl=da spell" will
> ask to download the files.
>
> I havent tried it much but it seems smart if the spell check files can
> be downloaded for a language and set the language at the same time so i
> dont have to figure out where to
Hey Bram,
I was a little confused by this patch, and I was hoping you'd enlighten me.
1. I see that the error messages from the test don't show up when I restored
'modifiable' in the original patch. So I didn't see them while working.
2. They also go away when using ":setlocal" instead of
> Why not collect all the translated help files the same place instead of
> all these different links to websites
> (https://www.vim.org/translations.php) that uses different way to get
> the files?
>
> Also some of the links dont work any longer.
> Persian and polish at the moment says not
I dont know much about Vim but i saw running ":set spl=da spell" will
ask to download the files.
I havent tried it much but it seems smart if the spell check files can
be downloaded for a language and set the language at the same time so i
dont have to figure out where to download and what
Keny Hu wrote:
> That makes sense. Thanks for the tip. Here is the updated indent file.
Thanks, I'll include this one.
--
hundred-and-one symptoms of being an internet addict:
126. You brag to all of your friends about your date Saturday night...but
you don't tell them it was only in a
Markus Braun wrote:
> I spend some more time reading the code. It seems that the member `vts` of
> struct `BalloonEval` needs to be initialized in `check_due_timer()` after
> allocating the storage. Otherwise the pointer `vts` has arbitrary value and
> `vim_free()` is called in
Patch 8.1.0121
Problem:Crash when using ballooneval related to 'vartabstop'.
Solution: Initialize balloonEval->vts to NULL. (Markus Braun)
Files: src/ex_cmds2.c, src/gui_beval.c, src/gui_w32.c, src/gui.c
*** ../vim-8.1.0120/src/ex_cmds2.c 2018-05-12 15:36:03.0 +0200
---
Patch 8.1.0120
Problem:Buffer 'modified' set even when :sort has no changes.
Solution: Only set 'modified' when lines are moved. (Jason Franklin)
Files: src/ex_cmds.c, src/testdir/test_sort.vim
*** ../vim-8.1.0119/src/ex_cmds.c 2018-06-24 23:53:25.149526513 +0200
---
Jason Franklin wrote:
> I noticed that the :sort command always sets 'modified'.
>
> This patch makes :sort check whether or not it actually changed
> the buffer.
>
> Tests included.
Thanks. One case where it is not correct: with "sort u" when the last
line is dropped. I'll correct that.
30 matches
Mail list logo
