> 1. are 1-wide
> 2. the *font itself* is too wide.
>
>
> So this problem has nothing to do with Vim.
>
>
> To check whether it is the case, use terminal emulator which does not support
> fallback fonts or does not do it by default. E.g. rxvt-unicode (AKA urxvt)
> has this property (make sure
On Tuesday, July 21, 2015 at 9:25:55 AM UTC+12, Yuri Vic wrote:
> I came across this symbol: U+1F44D THUMBS UP SIGN (đź‘Ť)
> In vim-7.4.778 it shows with width one or two...
And Zyx replied:
So this problem has nothing to do with Vim.
I agree. Using "Liberation Mono" with a GTK vim the thumbs up is
Hi Bram,
Thank you for merging my fix, but it looks like you have missed two files:
- runtime/doc/tags
- runtime/syntax/vim.vim
Please see attach.
--
Best regards,
Pavel
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are re
2015-07-21 0:25 GMT+03:00 Yuri Vic :
> I came across this symbol: U+1F44D THUMBS UP SIGN (đź‘Ť)
> In vim-7.4.778 it shows with width one or two, depending if the cursor is
> to the left of it or not. So the text in this line "jumps" when cursor
> moves over the symbol.
>
> Attaching example: thumbs.t
Hi all
Despite having used vim, “:help …” and “:helpgrep …” almost daily for 9 years
I was not aware of the special effect of the equal sign in `= … ` until
a recent bugreport from Pavol Juhas regarding this feature. Surprisingly
“:help improvements-6” hints, that this feature has been there si
Hi Pavol
On 2015-07-17 Friday at 10:47 -0400 Pavol Juhas wrote:
> On Fri, Jul 17, 2015 at 09:44:55AM +0200, Roland Eggner wrote:
> ...
> > On 2015-07-16 Thursday at 18:52 + v...@googlecode.com wrote:
> ...
> > > What steps will reproduce the problem?
> > >
> > > vim -u NONE -i NONE -N
I came across this symbol: U+1F44D THUMBS UP SIGN (đź‘Ť)
In vim-7.4.778 it shows with width one or two, depending if the cursor is
to the left of it or not. So the text in this line "jumps" when cursor
moves over the symbol.
Attaching example: thumbs.txt
Yuri
--
--
You received this message from
Axel Bender wrote:
> Given the attached file, do the following:
>
> :set ts=3 wrap showbreak=(cnt)
> /Sombrav2eUn.
>
> Here (Windows 7 64-bit, MinGW), only the letters until "...NOC" in the
> file's last line are converted to uppercase, "urna." is not converted.
Yes, that is wrong. Repeating
Jan Larres wrote:
> Bram Moolenaar :
> > + Note: It's a bad idea, to reset an option
> > + during this autocommand, since this will
> > + probably break plugins. You can always use
> > + |noa|
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 387 by fri...@google.com: Clicking gvim close window button is
interrupted by File Changed dialog.
https://code.google.com/p/vim/issues/detail?id=387
What steps will reproduce the problem?
1. Open a file in gvim.
2. Unfocus
Given the attached file, do the following:
:set ts=3 wrap showbreak=(cnt)
/Sombrav2eUn.
Here (Windows 7 64-bit, MinGW), only the letters until "...NOC" in the file's
last line are converted to uppercase, "urna." is not converted.
--
--
You received this message from the "vim_dev" maillist.
Do
Can anyone confirm this with Windows 7 64-bit (MinGW)?
--
--
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 sub
12 matches
Mail list logo
