Anyone else or just me? Erratic display bug

Using the latest gvim (at the moment, 8.0.823 but it started a few patchlevels ago) with Huge features, GTK2-GNOME2 GUI for linux x86_64. 'encoding' is "utf-8" and 'guifont' is set to "Bitstream Vera Sans Mono 8". (The double quotes are of course not part of the values.) Typing text interspersing

Error in configure argument in src/Makefile comment

Unlike what is said at line 343 of src/Makefile, --enable-gnome2-check is not recognized by configure. Nor does (AFAICT) --enable-gnome-check (without the 2) have any effect. It is possible to compile with Gnome2 though, but AFAICT this requires --enable-gui=gnome2, as mentioned at lines 369-370

Compile warning -Wmaybe-uninitialized in terminal.c at or maybe before 8.0.798

gvim with GTK3 GUI was so untractable recently on my new openSUSE 42.3 system that I decided to "downgrade" to GTK2, which of course means running "make reconfig" on the new set of configure parameters. This "full" compile gave the following warning, which did not prevent the generation of an (at

openSUSE Leap 42.3 was released yesterday

openSUSE Leap 42.3 (Linux) was released yesterday at noon GMT (1pm BST, 2pm CEST, etc.). I installed it, and it works "reasonably well". As always, if you compile your own Vim, I recommend running "make reconfig" immediately after any full OS upgrade. There are too many things that "just might"

Warning in Tiny buffer.c after patches 768 to 771

After applying patches 8.0.768 to 8.0.771, I get the following warning from gcc in the Tiny build (compile goes on, and link happens apparently satisfactorily): gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/buffer.o

Compile error in option.c for Tiny build after applying patches 754 to 763

After applying patches 754 to 763, cannot compile Tiny vim (Huge build has no error): gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/option.o option.c option.c:721:25: error: ‘PV_BH’ undeclared here (not in a

Re: Regression: Patch 7.4.709

FWIW, I also think that :tabmove 5 should move the current tab after what is now tab 5. Andy: when you do ":1,5move 10", where would you expect the present first 5 lines to go? After the present line 10 (becoming lines 5-10 after the move) or after the present line 15 (becoming lines 10-15 after

Incorrect tagging in runtime/doc/options.txt

Options.txt dated "Last change: 2017 Jul 15" At lines 7767 sqq, there is: *'thesaurus'* *'tsr'* 'termsize' 'tms'string(default "") local to window {not in Vi} etc. Line 7767 should say *'termsize'* *'tms'* instead. The tags for the

Inconsistent help for the new terminal feature

After setting $CONF_OPT_TERMINAL to '--enable-terminal' then running "make reconfig" followed by "make install" I notice the following in gvim: - Help tags are not defined yet for 'termkey' 'termsize' term_getsize() and term_setsize() - The output of :echo exists('+termkey')

Re: Off-by-one error for 'cmdheight' after patches 8.0.693 to 695

On Fri, Jul 7, 2017 at 1:53 PM, Christian Brabandt <cbli...@256bit.org> wrote: > > On Fr, 07 Jul 2017, Tony Mechelynck wrote: > >> On Fri, Jul 7, 2017 at 1:41 PM, Christian Brabandt <cbli...@256bit.org> >> wrote: >> > Is there an easy way to repro

Re: Off-by-one error for 'cmdheight' after patches 8.0.693 to 695

On Fri, Jul 7, 2017 at 1:48 PM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Fri, Jul 7, 2017 at 1:41 PM, Christian Brabandt <cbli...@256bit.org> wrote: >> Is there an easy way to reproduce this issue? >> >> Best, >> Christian > > Meanin

Re: Off-by-one error for 'cmdheight' after patches 8.0.693 to 695

On Fri, Jul 7, 2017 at 1:41 PM, Christian Brabandt wrote: > Is there an easy way to reproduce this issue? > > Best, > Christian Meaning you can't reproduce it by just running gvim? I don't know. I'll try restarting gvim and see if the problem goes away. Oh, and BTW there are

Off-by-one error for 'cmdheight' after patches 8.0.693 to 695

After manually adding symlinks in my shadow directories for ../libvterm and ../terminal.c I could successfully compile a Tiny and a Huge build. No change in configure settings, which for the Huge build are set as follows before running make: export CONF_OPT_GUI='--enable-gui=gtk3

8.0.661: maybe-uninitialized warning in term.c in Huge build but not in Tiny build

8.0.661: maybe-uninitialized warning in term.c in Huge build but not in Tiny build gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include

Re: [vim/vim] Default values for `QuickFixLine` make the selected entry in a quickfix window unreadable for many colorschemes (#1780)

On Tue, Jun 20, 2017 at 6:26 PM, justrajdeep wrote: > Hi > > I think this might have broken the some colorschemes also. I am using > peachpuff. If the line is too long I go to the end of the line and come back > the syntax highlight goes off. > > Thanks Maybe the

Re: Mouse actions not recognized in console vim in right part of the screen on very large displays

On Thu, Jun 15, 2017 at 9:04 AM, Christian Brabandt wrote: > > On Mi, 14 Jun 2017, George Karpenkov wrote: > >> Hi All, >> >> I have a rather strange bug running console vim on mac. >> I have a large imac (5120*2880 pixels), and in my terminal (I've tried both >> iterm2 and

Re: [vim/vim] Proposal: change 't' to position afTer the instead before it (#1759)

On Sat, Jun 10, 2017 at 3:19 PM, vim-dev ML wrote: > I am happy with the current function of f and t. > But I would like to know how to re-map t (or another char) such that it > would it would essentially do f(char)l. How to do f wait for (char) then do > l? I think an

Re: [vim/vim] Proposal: change 't' to position afTer the instead before it (#1759)

On Fri, Jun 9, 2017 at 6:40 PM, reTouche wrote: > No need to be negative, it's just a proposal. Instead of lecturing me you > could just write "Oh, no it's a great command, I use it all the time for..." > and give a specific example, or bring up any other reason.

Obsolete (incomplete) help for 'highlight'

AFAICT, the current default for the 'highlight' option is: (reformatted here by adding spaces to allow line-wrapping) 8:SpecialKey, ~:EndOfBuffer, @:NonText, d:Directory, e:ErrorMsg, i:IncSearch, l:Search, m:MoreMsg, M:ModeMsg, n:LineNr, N:CursorLineNr, r:Question, s:StatusLine, S:StatusLineNC,

Warning for unused label in Tiny build after applying patches 8.0.622-623

After applying patches 622-623, warning in Tiny build gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/regexp.o regexp.c regexp.c:362:15: warning: ‘e_large_class’ defined but not used [-Wunused-variable] static char_u

Re: Patch 8.0.0607

On Sun, Jun 4, 2017 at 3:33 PM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Sun, Jun 4, 2017 at 2:58 PM, Bram Moolenaar <b...@moolenaar.net> wrote: >> >> Patch 8.0.0607 >> Problem:When creating a bufref, then using :bwipe and :new it might g

Re: Patch 8.0.0607

On Sun, Jun 4, 2017 at 2:58 PM, Bram Moolenaar wrote: > > Patch 8.0.0607 > Problem:When creating a bufref, then using :bwipe and :new it might get > the same memory and bufref_valid() returns true. > Solution: Add br_fnum to check the buffer number didn't

Re: [vim/vim] In help documents, we should unify the spelling “Vim” or ”VIM". (#1732)

IMHO, if it's in all caps it should stay in all caps. So, either "Vim Reference Manual" or its all-caps variant, "VIM REFERENCE MANUAL", whichever is closer to what already exists, and if both versions exist in different files, let's standardize to which of the two occurs more often. Best

Re: [vim/vim] VIM should respect SIGINT (#1720)

Most "full" GUIs (programs which can be used _only_ as GUIs) respond in very similar manner to similar commands: on Linux, Ctrl-Q, and often but less reliably clicking the [x] at the end of the window titlebar, will make them exit gracefully. For interactive console programs it is different: to

Re: [vim/vim] Can we do something about "How to exit the Vim editor?" (#1719)

On Tue, May 23, 2017 at 8:31 PM, Roy Wellington Ⅳ wrote: > See this SO question for reference. > > The questioner is not asking a very well formed question here, to begin > with, which makes things hard. First, he seems to be seeing the prompt (but > misquotes it),

Re: [proposal][patch] Want to stop supporting troublesome options 'gdefault' and 'edcompatible'.

I'd rather remove as little existing stuff as possible, especially when (for someone who knows how to read the help) it is known to work as specified. Why not concentrate on the items in todo.txt before we start waving sabers around into the existing code? Best regards, Tony. -- -- You

Re: RFE: 'listchars' entry for soft-hyphen

On Mon, May 8, 2017 at 2:35 PM, Dominique Pellé <dominique.pe...@gmail.com> wrote: > Bram Moolenaar <b...@moolenaar.net> wrote: > >> Tony Mechelynck wrote: >> >>> I notice that at the moment, the soft-hyphen (U+00AD) is displayed as >>> a

Re: RFE: 'listchars' entry for soft-hyphen

On Thu, May 4, 2017 at 12:58 PM, Christian Brabandt <cbli...@256bit.org> wrote: > > On Do, 04 Mai 2017, Tony Mechelynck wrote: > >> Something must have gone wrong. >> >> After adding that custom syntax script, the string '' >> present in register x

Re: RFE: 'listchars' entry for soft-hyphen

at 12:08 PM, Christian Brabandt <cbli...@256bit.org> wrote: > > On Do, 04 Mai 2017, Tony Mechelynck wrote: > >> On Thu, May 4, 2017 at 8:27 AM, Christian Brabandt <cbli...@256bit.org> >> wrote: >> [...] >> > Is this really necessary? You can no

Re: RFE: 'listchars' entry for soft-hyphen

On Thu, May 4, 2017 at 8:27 AM, Christian Brabandt wrote: [...] > Is this really necessary? You can now use concealing to show arbitrary > code points differently. > > :call matchadd('Conceal', '\%uad', 10, -1, {'conceal': '↔'}) > :set conceallevel=2 concealcursor=nv [...]

RFE: 'listchars' entry for soft-hyphen

I notice that at the moment, the soft-hyphen (U+00AD) is displayed as a blank character cell. I suggest to add an entry in 'listchars' (e.g. shy:c) to display it as a glyph of the user's choice, so that e.g. :set lcs=eol:¶,tab:\|_,extends:>,precedes:<,conceal:*,nbsp:·,shy:↔ (assuming UTF-8

Re: Anybody using the Farsi feature?

On Wed, Apr 19, 2017 at 12:01 AM, Behdad Esfahbod wrote: > Humm. I don't like it that :set arabic activates a vim-side Arabic > keyboard. I run vim in gnome-terminal and want to use my X11 keyboards... > :set arabic, like :set nocompatible, :behave mswin, :vimdiff, :source

Re: modeline documentation is misleading

On Tue, Apr 11, 2017 at 5:26 PM, Bruno Bronosky wrote: > https://github.com/vim/vim/blame/e0720cbf63eb3045be8d965e3182c0c392c7b5e9/runtime/doc/options.txt#L505 > > The second form (this is compatible with some versions of Vi): > > >

Re: Anybody using the Farsi feature?

On Sun, Apr 9, 2017 at 2:47 PM, Bram Moolenaar wrote: > > Vim includes Farsi support. This implementation is quite old and uses > an encoding standard that is not widely used: ISIR-3342. In fact, > searching for that standard has the first 9 matches in Vim code. > It does

Re: [vim/vim] Invalid syntax highlighting inside string literals - it detects /* as a starting line for a comment (#1584)

On Wed, Mar 29, 2017 at 4:07 PM, Charles E Campbell wrote: > Simon Cornelius P. Umacob wrote: >> >> examplejs >> >> >> Copy-pasteable: >> >> |const init_env =` for i in

Re: [patch] *-register tests

On Fri, Mar 17, 2017 at 10:51 PM, Bram Moolenaar wrote: > On my system I don't have xsel. I'm afraid that this probably means > that most people don't have it. On my openSUSE Leap 42.2 system, xsel is not installed by default, but it is available on the OSS repository. If

Re: [vim/vim] Patch 446 mentioned twice in version.c (#1558)

On Mon, Mar 13, 2017 at 2:45 PM, Marius Gedminas wrote: > version.c includes patch 446 twice, which makes :version display > > Included patches: 1-446, 446-454 > I confirm the problem. AFAICT, there is only one patch 446, however, so the attached patch ought to fix it.

Re: Patch 8.0.0428

On Wed, Mar 8, 2017 at 10:06 AM, Christian Brabandt <cbli...@256bit.org> wrote: > Hi Tony! Hello Christian! > > On Mi, 08 Mär 2017, Tony Mechelynck wrote: > >> On Wed, Mar 8, 2017 at 9:52 AM, Dominique Pellé >> <dominique.pe...@gmail.com> wrote: >&g

Re: Patch 8.0.0428

On Wed, Mar 8, 2017 at 9:52 AM, Dominique Pellé <dominique.pe...@gmail.com> wrote: > Tony Mechelynck wrote: > >> P.S. .hgignore is missing a few additional files, present in >> .gitignore. See attached the revised patch. > > Hi Tony > > There is no .hgignore fil

Re: Patch 8.0.0428

P.S. .hgignore is missing a few additional files, present in .gitignore. See attached the revised patch. Best egards, Tony. On Wed, Mar 8, 2017 at 4:30 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Tue, Mar 7, 2017 at 9:27 PM, Bram Moolenaar <b...@moolenaa

Re: Patch 8.0.0428

On Tue, Mar 7, 2017 at 9:27 PM, Bram Moolenaar wrote: > > Patch 8.0.0428 > Problem:Git and hg see new files after running tests. (Manuel Ortega) > Solution: Add the generated file to .hgignore (or .gitignore). Delete the > resulting verbose file. (Christian

Re: Patch for quickfix.txt

On Tue, Mar 7, 2017 at 5:16 AM, 'Suresh Govindachar' via vim_dev wrote: > On 3/6/2017 2:02 PM, Bram Moolenaar wrote: >> >> Suresh Govindachar wrote: >>> >>> On 3/6/2017 6:17 AM, 'Suresh Govindachar' via vim_dev wrote: >> >> [...] >> Thanks. Let's use backticks for

Re: Problem installing 8.0.402 on Linux

There is a difference between sudo and su. Some things that root (or a "su root" console) can do, cannot be done by plain sudo. I don't know the fine points of these differences. If you install vim at the default location (with /usr/local/share/vim/vim80 as the $VIMRUNTIME of the runtime files,

Re: Patch 8.0.0380

On Sun, Feb 26, 2017 at 7:41 PM, Bram Moolenaar wrote: > > Patch 8.0.0380 > Problem:With 'linebreak' set and 'breakat' includes ">" a double-wide > character results in "<<" displayed. > Solution: Check for the character not to be replaced. (Ozaki Kiichi, >

Re: [vim/vim] Indent: bogus characters inserted in visual-block append

On Wed, Feb 22, 2017 at 1:19 PM, Christian Brabandt wrote: > Hi Vitor! > > On Mi, 22 Feb 2017, Vitor Antunes wrote: > >> On Tuesday, 6 December 2016 16:20:06 UTC, Christian Brabandt wrote: >> > Thanks, now I can confirm. >> > >> > Best, >> > Christian >> >> Although without

Re: Why is the MacOS port of Vim not part of the mainline Vim?

On Wed, Feb 22, 2017 at 11:25 AM, Yegappan Lakshmanan wrote: > Hi all, > > Why is the native MacOS port of Vim not part of the mainline > Vim source and is maintained in a separate repository? > > https://github.com/macvim-dev/macvim > > The above branch is actively synced

Re: RFE: Add (U+00AD) to listchars

On Fri, Feb 17, 2017 at 11:14 AM, Matěj Cepl wrote: > Hi, > > would it be possible to do something about display of the soft > hyphen character (U+00AD)? I tried to use it in my rST file, but > ended up with a blank space. So I filed a bug against the font > I use

Re: [vim/vim] Is 'backup' supposed to be off by default? (#1468)

On Sun, Feb 12, 2017 at 5:17 AM, thecliguy wrote: > I am running the following version of Vim on Windows 10: > > VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Nov 6 2016 17:05:36) > MS-Windows 32-bit console version > Included patches: 1-69 Note that the latest

Re: [vim/vim] Is 'backup' supposed to be off by default? (#1468)

On Sun, Feb 12, 2017 at 1:56 PM, K.Takata wrote: > Current Windows installer creates a system vimrc which includes > vimrc_example.vim, but it is not documented as far as I know. > Now Vim 8.0 has defaults.vim and it is well documented. Maybe the Windows > installer

Re: [vim/vim] printf("%p") is useless (#1466)

On Sat, Feb 11, 2017 at 7:31 PM, vim-dev ML wrote: > Hi Nikolai, > > Excuse, This has nothing to do with the subject, will not you stop using > `VimL`? > GitHub ceased using VimL. > See the attached image. > -- > Best regards, > Hirohito Higashi (a.k.a. h_east) I

Documentation bug: How to search help for a pattern (Was: Patch 8.0.0315)

resent help text, is of course superfluous but not harmful.) Best regards, Tony. On Thu, Feb 9, 2017 at 7:33 AM, Christian Brabandt <cbli...@256bit.org> wrote: > On Mi, 08 Feb 2017, Bram Moolenaar wrote: > >> Patch 8.0.0315 >> Problem:":help :[range]" doe

Re: Cannot find helptag :[range]

On Thu, Feb 9, 2017 at 12:14 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > P.S. I'll retry with patch 8.0.315. ...once it appears on the Mercurial mirror (it hasn't yet). Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not

Re: Cannot find helptag :[range]

P.S. I'll retry with patch 8.0.315. On Thu, Feb 9, 2017 at 12:12 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Wed, Feb 8, 2017 at 11:11 PM, Bram Moolenaar <b...@moolenaar.net> wrote: >> >> Tony Mechelynck wrote: >> >>> The helptag :

Re: Cannot find helptag :[range]

On Wed, Feb 8, 2017 at 11:11 PM, Bram Moolenaar <b...@moolenaar.net> wrote: > > Tony Mechelynck wrote: > >> The helptag :[range] is defined at line 334 of helpfile motion.txt. >> But it cannot be found. When I do >> >> :help :[range] >> >> I

Cannot find helptag :[range]

The helptag :[range] is defined at line 334 of helpfile motion.txt. But it cannot be found. When I do :help :[range] I get to helptag :r instead, at line 1901 of helpfile insert.txt, and that even after doing ":helptags $VIMRUNTIME/doc" and even by selecting :[range] in the wildmenu on (for

Build error in Tiny (Was: Patch 8.0.0259)

On Sun, Jan 29, 2017 at 3:10 PM, Bram Moolenaar wrote: > > Patch 8.0.0259 > Problem:Tab commands do not handle count correctly. (Ken Hamada) > Solution: Add ADDR_TABS_RELATIVE. (Hirohito Higashi) > Files: runtime/doc/tabpage.txt, src/ex_cmds.h, src/ex_docmd.c, >

RFE: ambiguity under :help printf()

Line 5977 of the eval.txt helpfile says: %Gfloating point number, as %f or %E depending on value This is ambiguous if the value is NaN or ±INF: is the result in upper case (as for %E) or in lower case (as for %f)? I propose to replace %f by %F in that line to remove the ambiguity,

Re: Patch 8.0.0223

On Mon, Jan 23, 2017 at 8:47 PM, Bram Moolenaar wrote: > > Patch 8.0.0223 > Problem:Coverity gets confused by the flags passed to find_tags() and > warnts for an uninitialized variable. > Solution: Disallow using cscope and help tags at the same time. >

Re: Patch 8.0.0198

On Tue, Jan 17, 2017 at 4:27 PM, Bram Moolenaar wrote: > > Patch 8.0.0198 > Summary:some syntax arguments take effect even after "if 0" > Problem:Some syntax arguments take effect even after "if 0". (Taylor > Venable) > Solution: Properly skip the syntax

Re: [vim/vim] <C-]> issue using Portuguese-Brazil keyboard layout (#1378)

On Fri, Jan 13, 2017 at 6:31 PM, Eduardo Sousa wrote: > When I'm using a portuguese keyboard layout, and I press , vim > identifies it as , which makes me unable to navigate help files using > this kind of keyboards Finding a specific control key for a

Re: [bug] vim+tmux: current line changes when using mouse to switch between buffers

On Thu, Jan 12, 2017 at 11:10 PM, Jon Seidel wrote: > I use vim in a tmux window a lot. And when I open a session (using > OpenSession) I usually have a number of buffers open. > > I use the mouse to switch between buffers; when I click in a buffer with the > mouse, the the

Intermittent bug: off-by-one error in 'cmdheight'

At the moment I cannot reproduce it at will, but at times I see a command-line window one fewer line high than the value set in my vimrc by if exists('+cmdheight') && ( < 2) set ch=2 endif Once it appears, ":set ch=4" gives me only 3 lines of command-line height, and then ":set ch=2" brings it

Re: Why make visual mode default? This editor is now useless to me.

On Wed, Dec 21, 2016 at 5:37 PM, Ervin Ruci wrote: > After your recent update the behavior of the mouse changed. > > Selecting some text with the mouse automatically enters visual mode. I rarely > use the visual feature and when I use it I prefer using the v keyboard >

Re: [patch] added tests for float functions

Unary + and unary - are accepted as operators for Numbers in vimscript. Floats are not expressly mentioned under ":help expr7" but I would expect them to be "some kind of number", thus + 1.2 should be a legitimate expression (1.2, unchanged) and so would - 1.2 (1.2, with sign change). These

Re: [vim/vim] Right click enables visual mode by default (#1326)

On Wed, Dec 14, 2016 at 7:04 AM, Mas wrote: > Referencing issue # 1188 > I am wondering if this is a bug or by design in VIM 8? The same is happening > via Fedora 25. When right clicking it puts you into visual mode. The only > fix is to add set mouse-=a or set mouse=

Re: [vim/vim] patch 7.4.2111 (8c08b5b)

On Wed, Nov 23, 2016 at 5:08 PM, James McCoy wrote: > It could be an issue for anyone that didn't have a .vimrc file. > > Correct, and there are far more of those than I would have expected. > > I think root would be the most popular of that class of users. > > Right,

Re: [vim/vim] Fix parallel make of object files (#1259)

On Fri, Nov 18, 2016 at 8:48 AM, Marius Gedminas wrote: > @mgedmin commented on this pull request. > > > > In src/Makefile: > >> > -objects/arabic.o: arabic.c > +objects/arabic.o: objects arabic.c > > You should use an order-only

Re: Netrw doesn't work on Windows correctly. Please permit us to modify code on github.com

On Wed, Nov 9, 2016 at 2:12 AM, mattn wrote: > On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote: >> Cesar Romani wrote: > >> Netrw actually doesn't check that expand("$COMSPEC") is execuable before >> setting up g:netrw_localcopycmd; instead, it uses that if

Warning in Tiny build (but not in Guge build) at patchlevel 8.0.0062

After pulling 8.0.0055 to 8.0.0062, I get the following warning in the Tiny build but not in the Huge build: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/option.o option.c option.c:5830:1: warning:

Re: gvim and ASCII glyphs

On Thu, Oct 27, 2016 at 2:08 AM, Matěj Cepl <mc...@cepl.eu> wrote: > On 2016-10-26, 22:23 GMT, Tony Mechelynck wrote: >> Don't make the too frequent error to believe that everyone >> else, or at least most of them, has the same preferences as >> you. The fact that we h

Re: gvim and ASCII glyphs

On Wed, Oct 26, 2016 at 8:32 PM, Matěj Cepl wrote: > On 2016-10-26, 17:26 GMT, Charles E Campbell wrote: >> If you're using utf-8, its easy to get the glyph transform >> with mathmenu.vim (comes with >> http://www.drchip.org/astronaut/vim/index.html#MATH): type >=, select >> with

Re: ":set cmdheight=2" doesn't work

gvim 8.0.0041 seems unaffected and yet the description of patch 41 seems to be for something else. I shall have to check if and when the problem reappears. Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

Re: ":set cmdheight=2" doesn't work

Oops: I meant ":wa | wv" On Sun, Oct 16, 2016 at 4:04 PM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > I don't know exactly when this appeared but gvim 8.0.0040 (Huge, GTK3, > Linux64) is affected. > > After ":set cmdheight=2" the command -line h

Re: ":set cmdheight=2" doesn't work

On Sun, Oct 16, 2016 at 4:04 PM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > I don't know exactly when this appeared but gvim 8.0.0040 (Huge, GTK3, > Linux64) is affected. > > After ":set cmdheight=2" the command -line height (between the bottom > statu

":set cmdheight=2" doesn't work

I don't know exactly when this appeared but gvim 8.0.0040 (Huge, GTK3, Linux64) is affected. After ":set cmdheight=2" the command -line height (between the bottom statusline and the bottom of the Vim GUI) is still only one line, and after ":xa | wv", which generates two lines of output, I get a

vmaps in matchit.vim

The matchit plugin (1.13.2, for Vim 6.3+, Last Change: 2016 Aug 21) uses :vmap commands, defining common mappings for both Visual and Select mode. For instance: 55> vnoremap % :call Match_wrapper('',1,'v') m'gv`` 56> vnoremap g% :call Match_wrapper('',0,'v') m'gv`` 63> vmap [% [%m'gv`` 64>

Re: Patch 8.0.0009

On Sun, Sep 25, 2016 at 8:22 PM, Bram Moolenaar wrote: > > Patch 8.0.0009 > Problem:Unecessary workround for AppVeyor. > Solution: Revert patch 7.4.990. (Christian Brabandt) > Files: appveyor.yml appveyor.yml includes the following section near the end:

Re: [vim/vim] character bottom padding is twice top padding？ (#1113)

If you mean that there is more space below capital-letter glyphs than above them, this is normal: indeed, descenders (as with g, j, p, q) go below the capitals' baseline, while ascenders (as in b, d, f, h, k, l, t) hardly go above the capitals' top line. Instead of comparing the blank space above

Re: exists() result sometimes misleading for a command

Ah, I see. Under GTK3 I can't anymore tearoff the menus, even manually. Best regards, Tony. On Sun, Sep 18, 2016 at 2:13 AM, James McCoy <james...@jamessan.com> wrote: > On Sun, Sep 18, 2016 at 01:25:53AM +0200, Tony Mechelynck wrote: >> A few weeks ago, when I was still bui

Re: exists() result sometimes misleading for a command

On Fri, Sep 16, 2016 at 11:02 AM, Kazunobu Kuriyama <kazunobu.kuriy...@gmail.com> wrote: > 2016-09-15 16:45 GMT+09:00 Kazunobu Kuriyama <kazunobu.kuriy...@gmail.com>: >> >> 2016-09-15 7:41 GMT+09:00 Tony Mechelynck <antoine.mechely...@gmail.com>: >>> &

Re: exists() result sometimes misleading for a command

On Thu, Sep 15, 2016 at 11:22 AM, Kazunobu Kuriyama <kazunobu.kuriy...@gmail.com> wrote: > 2016-09-15 17:46 GMT+09:00 Tony Mechelynck <antoine.mechely...@gmail.com>: >> >> On Thu, Sep 15, 2016 at 9:45 AM, Kazunobu Kuriyama >> <kazunobu.kuriy...@gmail.com> wro

Re: exists() result sometimes misleading for a command

On Thu, Sep 15, 2016 at 9:45 AM, Kazunobu Kuriyama <kazunobu.kuriy...@gmail.com> wrote: > 2016-09-15 7:41 GMT+09:00 Tony Mechelynck <antoine.mechely...@gmail.com>: >> >> exists() result is sometimes misleading for a command. >> >> Example (with GTK3 gvi

exists() result sometimes misleading for a command

exists() result is sometimes misleading for a command. Example (with GTK3 gvim linked with GTK 3.16.7): :echo exists(':tearoff') 2 :tearoff E319: Sorry, the command is not available in this version So for example the following code in my vimrc would produce the exact

Re: [vim/vim] Cname for vim.org to point to www.vim.org (#1062)

Some browsers, including by default Firefox and SeaMonkey, will look up www.something.tld if something.tld isn't found. This feature can be disabled by means of a preference, however, so it may or may not be a problem for you. For me it isn't. Best regards, Tony. On Mon, Sep 12, 2016 at 11:10

Re: update to the documentation

On Fri, Sep 9, 2016 at 1:41 PM, Bram Moolenaar wrote: > The logic for whether the .vimrc file is used is quite complicated. > That's why we can't make this decision before loading a system vimrc. > > I think it's easier to suggest unletting skip_defaults_vim always: > > > This

Re: update to the documentation

On Fri, Sep 9, 2016 at 1:14 PM, Bram Moolenaar wrote: > > Christian Brabandt wrote: > >> here is a small update to the documentation that mentions how to skip >> loading the defaults.vim file >> >> diff --git a/runtime/doc/starting.txt b/runtime/doc/starting.txt >> index

Re: update to the documentation

On Fri, Sep 9, 2016 at 9:55 AM, Christian Brabandt wrote: > Bram, > here is a small update to the documentation that mentions how to skip > loading the defaults.vim file > > diff --git a/runtime/doc/starting.txt b/runtime/doc/starting.txt > index 14a5f01..2142343 100644 > ---

Re: Erroneous positioning of cursor with multibyte characters

On Thu, Sep 8, 2016 at 2:26 AM, Eric Pruitt <eric.pru...@gmail.com> wrote: > On Thu, Sep 08, 2016 at 12:48:00AM +0200, Tony Mechelynck wrote: >> IMHO the proper fix for this would be to select a better ("less >> buggy", "more modern") font face in your ter

Re: Erroneous positioning of cursor with multibyte characters

On Wed, Sep 7, 2016 at 4:40 PM, Eric Pruitt <eric.pru...@gmail.com> wrote: > On Wed, Sep 07, 2016 at 09:04:27AM +0200, Tony Mechelynck wrote: >> This is not broken Unicode support. According to >> http://www.unicode.org/Public/UCD/latest/ucd/EastAsianWidth.txt (the >> l

Re: Erroneous positioning of cursor with multibyte characters

On Wed, Sep 7, 2016 at 6:38 AM, Eric Pruitt wrote: > On Sun, Aug 28, 2016 at 05:58:48PM -0700, Eric Pruitt wrote: >> On Sun, Aug 28, 2016 at 05:26:01PM -0700, Eric Pruitt wrote: >> > I am Vim 7.4.2289, and I have noticed a problem with multibyte >> > characters and the

Re: unexpected "ad behavior

On Wed, Sep 7, 2016 at 7:06 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Wed, Sep 7, 2016 at 6:22 AM, Charles E Campbell > <drc...@campbellfamily.biz> wrote: >> Hello: >> >> With the following 6 lines: (the last three are empty) >> --

Re: unexpected "ad behavior

On Wed, Sep 7, 2016 at 6:22 AM, Charles E Campbell wrote: > Hello: > > With the following 6 lines: (the last three are empty) > - > hello world! > hello world! > hello world! > > > > - > Put cursor on line 4, use ctrl-v and move down 2

Re: Patch 7.4.2319

On Sat, Sep 3, 2016 at 8:09 PM, Bram Moolenaar wrote: > > Patch 7.4.2319 > Problem:No way for a system wide vimrc to stop loading defaults.vim. > (Christian Hesse) > Solution: Bail out of defaults.vim if skip_defaults_vim was set. > Files:

Re: [vim/vim] defaults.vim overwrites /etc/vimrc (#1033)

On Sat, Sep 3, 2016 at 4:25 AM, David Fishburn wrote: > > On Fri, Sep 2, 2016 at 4:24 PM, Christian Hesse > wrote: >> >> Since version 7.4.2111 we load a less conservative defaults.vim file if >> ~/.vimrc is not found. These options can not be

Re: [vim/vim] gvim exits with "BadWindow (invalid window parameter)" when highlighting large regions (#1023)

On Wed, Aug 31, 2016 at 6:44 PM, Antony Lee wrote: > See above. > See what above? Please do the following in the gvim version where you experience the problem: :redir > ~/vim-version.txt :version :redir END then attach the resulting ~/vim-version.txt to a reply

warning in message.c in tiny build (ifdef missing in patch 2280?)

gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/message.o message.c message.c:3998:1: warning: ‘infinity_str’ defined but not used [-Wunused-function] infinity_str(int positive, ^ - No warning in Huge build with +float

Re: Does the visual bell work in GTK+ 3?

On Thu, Aug 25, 2016 at 3:13 PM, Kazunobu Kuriyama <kazunobu.kuriy...@gmail.com> wrote: > 2016-08-25 3:09 GMT+09:00 Tony Mechelynck <antoine.mechely...@gmail.com>: >> >> On Wed, Aug 24, 2016 at 8:03 PM, Tony Mechelynck >> <antoine.mechely...@gmail.com> wrot

Re: Does the visual bell work in GTK+ 3?

On Wed, Aug 24, 2016 at 8:03 PM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Wed, Aug 24, 2016 at 7:17 PM, Kazunobu Kuriyama > <kazunobu.kuriy...@gmail.com> wrote: >> Beep ((sound) bell) is implemented in both GTK+ 2 and GTK +3 using >> gdk_disp

Re: Does the visual bell work in GTK+ 3?

On Wed, Aug 24, 2016 at 7:17 PM, Kazunobu Kuriyama wrote: > Beep ((sound) bell) is implemented in both GTK+ 2 and GTK +3 using > gdk_display_bell() (gui_gtk_x11.c:6222, gui_mch_beep()), and there's no > interdependency between beep and visual bell. Accordingly,

Re: Does the visual bell work in GTK+ 3?

On Wed, Aug 24, 2016 at 12:08 PM, Kazunobu Kuriyama <kazunobu.kuriy...@gmail.com> wrote: > 2016-08-24 4:45 GMT+09:00 Tony Mechelynck <antoine.mechely...@gmail.com>: >> >> With the following settings: >> >> :verbose set eb? vb? bo? t_vb? >>

<    2   3   4   5   6   7   8   9   10   11   >