On Tue, Apr 30, 2019 at 11:22 PM 'Lifepillar' via vim_use
<vim_use@googlegroups.com> wrote:
>
> I have made some colorschemes that use colors 0-15 or 16-256 according to the
> value of t_Co or based on a user option:
>
> if &t_Co < 256 || g:mytheme_force16colors = 1
> # Define hi groups with colors 0-15
> else
> # Define hi groups with colors 16-256
> endif
>
> Setting t_Co at runtime appears to cause the colorscheme to reload, so it seems
> that the user option above is redundant. Is there any reason why one should
> avoid changing t_Co at runtime or is it ok to set t_Co to reload the
> colorscheme with a different configuration?
>
> Thanks,
> Life.
Well, the only reason I can imagine of having to set t_Co at runtime
would be because a badly set $TERM causes t_Co to be set to something
else than what the terminal actually supports. In that case the right
place to change t_Co would be in the vimrc, before loading any
colorscheme. For instance, on my system AFAIK all terminals support
256 colors _except_ the text-only Linux console (Ctrl-Alt-F2 or
similar) so my vimrc includes the following:
" set many-colors mode on terminals other than the Linux console
if !has('gui_running') && &term !~# "^linux" && &t_Co <=16
set t_Co=256
endif
Other than that, I don't touch t_Co. The reason I test "&& &t_Co <=
16" is that if some terminal has a $TERM setting resulting in, say, a
t_Co of 88, then that's probably correct.
Now in you find out in the middle of a Vim session that t_Co is set to
a wrong value, you can probably set it then manually with no ill
effects, or at least nothing worse than what you were already having,
i.e., wrong display colors. After that, you may or may not (I'm not
sure) have to reload your colrscheme.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tuesday, April 30, 2019
Re: Grouping digraphs
On 30 Apr 2019, at 13:13, Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
> But (@Lifepillar) Christian is too modest — another great tool for
> (among others) searching for and identifying Unicode characters is his
> own unicode.vim plugin (which includes online help according to the
> great Vim tradition):
> * stable version, https://www.vim.org/scripts/script.php?script_id=2822
> * development version, https://github.com/chrisbra/unicode.vim
That looks like a very useful plugin.
Thanks!
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> But (@Lifepillar) Christian is too modest — another great tool for
> (among others) searching for and identifying Unicode characters is his
> own unicode.vim plugin (which includes online help according to the
> great Vim tradition):
> * stable version, https://www.vim.org/scripts/script.php?script_id=2822
> * development version, https://github.com/chrisbra/unicode.vim
That looks like a very useful plugin.
Thanks!
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tweaking t_Co to configure colorscheme
I have made some colorschemes that use colors 0-15 or 16-256 according to the
value of t_Co or based on a user option:
if &t_Co < 256 || g:mytheme_force16colors = 1
# Define hi groups with colors 0-15
else
# Define hi groups with colors 16-256
endif
Setting t_Co at runtime appears to cause the colorscheme to reload, so it seems
that the user option above is redundant. Is there any reason why one should
avoid changing t_Co at runtime or is it ok to set t_Co to reload the
colorscheme with a different configuration?
Thanks,
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
value of t_Co or based on a user option:
if &t_Co < 256 || g:mytheme_force16colors = 1
# Define hi groups with colors 0-15
else
# Define hi groups with colors 16-256
endif
Setting t_Co at runtime appears to cause the colorscheme to reload, so it seems
that the user option above is redundant. Is there any reason why one should
avoid changing t_Co at runtime or is it ok to set t_Co to reload the
colorscheme with a different configuration?
Thanks,
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Grouping digraphs
On Tue, Apr 30, 2019 at 7:45 AM Christian Brabandt <cblists@256bit.org> wrote:
> On Mo, 29 Apr 2019, 'Lifepillar' via vim_use wrote:
>
> > I recall reading about a proposal (by C. Brabandt, I think) for grouping
> > the presentation of digraphs. I don't seem to be able to find that
> > discussion, however. Does anyone know the status of the proposal and
> > whether there is a patch available to try?
>
> It has been included. Use the `:digraphs!` command.
>
Thanks for mentioning.
But (@Lifepillar) Christian is too modest — another great tool for
(among others) searching for and identifying Unicode characters is his
own unicode.vim plugin (which includes online help according to the
great Vim tradition):
* stable version, https://www.vim.org/scripts/script.php?script_id=2822
* development version, https://github.com/chrisbra/unicode.vim
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Mo, 29 Apr 2019, 'Lifepillar' via vim_use wrote:
>
> > I recall reading about a proposal (by C. Brabandt, I think) for grouping
> > the presentation of digraphs. I don't seem to be able to find that
> > discussion, however. Does anyone know the status of the proposal and
> > whether there is a patch available to try?
>
> It has been included. Use the `:digraphs!` command.
>
Thanks for mentioning.
But (@Lifepillar) Christian is too modest — another great tool for
(among others) searching for and identifying Unicode characters is his
own unicode.vim plugin (which includes online help according to the
great Vim tradition):
* stable version, https://www.vim.org/scripts/script.php?script_id=2822
* development version, https://github.com/chrisbra/unicode.vim
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Monday, April 29, 2019
Re: Grouping digraphs
On 30 Apr 2019, at 07:44, Christian Brabandt <cblists@256bit.org> wrote:
>
>
> On Mo, 29 Apr 2019, 'Lifepillar' via vim_use wrote:
>
>> I recall reading about a proposal (by C. Brabandt, I think) for grouping
>> the presentation of digraphs. I don't seem to be able to find that
>> discussion, however. Does anyone know the status of the proposal and
>> whether there is a patch available to try?
>>
>> Digraphs are a wonderful feature, except that finding a specific symbol
>> is often time-consuming. E.g., to type Cyrillic or Greek or math, it
>> would be much easier if there were "Cyrillic", "Greek", "Math", etc…
>> sections in the :digraphs output.
>
> It has been included. Use the `:digraphs!` command.
Awesome!
Thanks,
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
>
> On Mo, 29 Apr 2019, 'Lifepillar' via vim_use wrote:
>
>> I recall reading about a proposal (by C. Brabandt, I think) for grouping
>> the presentation of digraphs. I don't seem to be able to find that
>> discussion, however. Does anyone know the status of the proposal and
>> whether there is a patch available to try?
>>
>> Digraphs are a wonderful feature, except that finding a specific symbol
>> is often time-consuming. E.g., to type Cyrillic or Greek or math, it
>> would be much easier if there were "Cyrillic", "Greek", "Math", etc…
>> sections in the :digraphs output.
>
> It has been included. Use the `:digraphs!` command.
Awesome!
Thanks,
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Grouping digraphs
On Mo, 29 Apr 2019, 'Lifepillar' via vim_use wrote:
> I recall reading about a proposal (by C. Brabandt, I think) for grouping
> the presentation of digraphs. I don't seem to be able to find that
> discussion, however. Does anyone know the status of the proposal and
> whether there is a patch available to try?
>
> Digraphs are a wonderful feature, except that finding a specific symbol
> is often time-consuming. E.g., to type Cyrillic or Greek or math, it
> would be much easier if there were "Cyrillic", "Greek", "Math", etc…
> sections in the :digraphs output.
It has been included. Use the `:digraphs!` command.
Best,
Christian
--
Man muß manchmal von einem Menschen fortgehen, um ihn zu finden.
-- Heimito von Doderer (Pseudonym: Stangeler, Reneé)
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I recall reading about a proposal (by C. Brabandt, I think) for grouping
> the presentation of digraphs. I don't seem to be able to find that
> discussion, however. Does anyone know the status of the proposal and
> whether there is a patch available to try?
>
> Digraphs are a wonderful feature, except that finding a specific symbol
> is often time-consuming. E.g., to type Cyrillic or Greek or math, it
> would be much easier if there were "Cyrillic", "Greek", "Math", etc…
> sections in the :digraphs output.
It has been included. Use the `:digraphs!` command.
Best,
Christian
--
Man muß manchmal von einem Menschen fortgehen, um ihn zu finden.
-- Heimito von Doderer (Pseudonym: Stangeler, Reneé)
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Grouping digraphs
I recall reading about a proposal (by C. Brabandt, I think) for grouping
the presentation of digraphs. I don't seem to be able to find that
discussion, however. Does anyone know the status of the proposal and
whether there is a patch available to try?
Digraphs are a wonderful feature, except that finding a specific symbol
is often time-consuming. E.g., to type Cyrillic or Greek or math, it
would be much easier if there were "Cyrillic", "Greek", "Math", etc…
sections in the :digraphs output.
Thanks,
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
the presentation of digraphs. I don't seem to be able to find that
discussion, however. Does anyone know the status of the proposal and
whether there is a patch available to try?
Digraphs are a wonderful feature, except that finding a specific symbol
is often time-consuming. E.g., to type Cyrillic or Greek or math, it
would be much easier if there were "Cyrillic", "Greek", "Math", etc…
sections in the :digraphs output.
Thanks,
Life.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
On Mo, 29 Apr 2019, Jeenu wrote:
> On Monday, April 15, 2019 at 8:15:19 PM UTC+1, Christian Brabandt wrote:
> > There was an issue about Vim not correctly resetting up the X
> > connection, (I believe #3649) and a fix seems to have been included by
> > 8.1.0615.
>
> From the observations I've made so far, it does seem like X server disconnection/restart is causing this problem.
>
> My reading is that https://github.com/vim/vim/pull/844 is the PR that has a fix, but hasn't been merged yet.
>
> I'm currently using a prebuilt 8.1.1139, which supposedly contains the "fix" mentioned in https://github.com/vim/vim/issues/3649#issuecomment-449705992, but I observe the same issue as before.
>
> So I suppose I wait until #844 is merged.
Try increasing the limits mentioned here:
https://github.com/vim/vim/issues/3649#issuecomment-445868123
You need to recompile.
Best,
Christian
--
Jedem Narren gefällt seine Kappe.
-- Sprichwort
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Monday, April 15, 2019 at 8:15:19 PM UTC+1, Christian Brabandt wrote:
> > There was an issue about Vim not correctly resetting up the X
> > connection, (I believe #3649) and a fix seems to have been included by
> > 8.1.0615.
>
> From the observations I've made so far, it does seem like X server disconnection/restart is causing this problem.
>
> My reading is that https://github.com/vim/vim/pull/844 is the PR that has a fix, but hasn't been merged yet.
>
> I'm currently using a prebuilt 8.1.1139, which supposedly contains the "fix" mentioned in https://github.com/vim/vim/issues/3649#issuecomment-449705992, but I observe the same issue as before.
>
> So I suppose I wait until #844 is merged.
Try increasing the limits mentioned here:
https://github.com/vim/vim/issues/3649#issuecomment-445868123
You need to recompile.
Best,
Christian
--
Jedem Narren gefällt seine Kappe.
-- Sprichwort
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
On Monday, April 15, 2019 at 8:15:19 PM UTC+1, Christian Brabandt wrote:
> There was an issue about Vim not correctly resetting up the X
> connection, (I believe #3649) and a fix seems to have been included by
> 8.1.0615.
From the observations I've made so far, it does seem like X server disconnection/restart is causing this problem.
My reading is that https://github.com/vim/vim/pull/844 is the PR that has a fix, but hasn't been merged yet.
I'm currently using a prebuilt 8.1.1139, which supposedly contains the "fix" mentioned in https://github.com/vim/vim/issues/3649#issuecomment-449705992, but I observe the same issue as before.
So I suppose I wait until #844 is merged.
--
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> There was an issue about Vim not correctly resetting up the X
> connection, (I believe #3649) and a fix seems to have been included by
> 8.1.0615.
From the observations I've made so far, it does seem like X server disconnection/restart is causing this problem.
My reading is that https://github.com/vim/vim/pull/844 is the PR that has a fix, but hasn't been merged yet.
I'm currently using a prebuilt 8.1.1139, which supposedly contains the "fix" mentioned in https://github.com/vim/vim/issues/3649#issuecomment-449705992, but I observe the same issue as before.
So I suppose I wait until #844 is merged.
--
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Saturday, April 27, 2019
Re: When selecting text the cursor jumps in a weird way
On Sat, 27 Apr 2019 21:23:58 -0400
Wolf Bogacz <wbogacz@gmail.com> wrote:
> This is just a theory based on what I understand your symptoms to be.
>
> Check the settings and their meanings of scrolloff and scrolljump, and
> where they are/were set.
>
> :verbose set scrolloff?
> :verbose set scrolljump?
>
> Then interpret their meanings as they apply to your conditions.
> :he scrolloff
> and
> :he scrolljump
>
Very interesting. Thanks for this.
Now, I found out what happenend.
After I started the selection, i.e pressed <Shift-v> I immediately
pressed the down arrow key. The Shift key wasn't yet released and I
ended up with <S-Down> which scrolled a half page down. This explains
why it didn't always happen.
As I never use <S-Down> I have remapped it:
noremap <S-Up> <Up>
noremap <S-Down> <Down>
Now things are fine.
--
Manfred
> On Sat, Apr 27, 2019 at 3:40 PM Manfred Lotz <ml_news@posteo.de>
> wrote:
>
> > I don't know exactly how to describe my problem.
> >
> > I have started gvim and loaded a file.
> >
> > The cursor goes to line 215 and the last visible lines in the gvim
> > window are line numbers 215 and 216.
> >
> > Now I type V, and go down to select lines of text.
> >
> > Very quickly, the buffer gets redisplayed in a way that now lines
> > 219 and 220 are at the beginning of the gvim window which is weird
> > as lines 215-218 are no longer visible. This is very irritating.
> >
> > Is there anything I can do to prevent this?
> >
> > --
> > Manfred
> >
> > --
> > --
> > You received this message from the "vim_use" 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 Google
> > Groups "vim_use" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to vim_use+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wolf Bogacz <wbogacz@gmail.com> wrote:
> This is just a theory based on what I understand your symptoms to be.
>
> Check the settings and their meanings of scrolloff and scrolljump, and
> where they are/were set.
>
> :verbose set scrolloff?
> :verbose set scrolljump?
>
> Then interpret their meanings as they apply to your conditions.
> :he scrolloff
> and
> :he scrolljump
>
Very interesting. Thanks for this.
Now, I found out what happenend.
After I started the selection, i.e pressed <Shift-v> I immediately
pressed the down arrow key. The Shift key wasn't yet released and I
ended up with <S-Down> which scrolled a half page down. This explains
why it didn't always happen.
As I never use <S-Down> I have remapped it:
noremap <S-Up> <Up>
noremap <S-Down> <Down>
Now things are fine.
--
Manfred
> On Sat, Apr 27, 2019 at 3:40 PM Manfred Lotz <ml_news@posteo.de>
> wrote:
>
> > I don't know exactly how to describe my problem.
> >
> > I have started gvim and loaded a file.
> >
> > The cursor goes to line 215 and the last visible lines in the gvim
> > window are line numbers 215 and 216.
> >
> > Now I type V, and go down to select lines of text.
> >
> > Very quickly, the buffer gets redisplayed in a way that now lines
> > 219 and 220 are at the beginning of the gvim window which is weird
> > as lines 215-218 are no longer visible. This is very irritating.
> >
> > Is there anything I can do to prevent this?
> >
> > --
> > Manfred
> >
> > --
> > --
> > You received this message from the "vim_use" 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 Google
> > Groups "vim_use" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to vim_use+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: When selecting text the cursor jumps in a weird way
This is just a theory based on what I understand your symptoms to be.
Check the settings and their meanings of scrolloff and scrolljump, and where they are/were set.
:verbose set scrolloff?
:verbose set scrolljump?
Then interpret their meanings as they apply to your conditions.
:he scrolloff
and
:he scrolljump
On Sat, Apr 27, 2019 at 3:40 PM Manfred Lotz <ml_news@posteo.de> wrote:
I don't know exactly how to describe my problem.
I have started gvim and loaded a file.
The cursor goes to line 215 and the last visible lines in the gvim
window are line numbers 215 and 216.
Now I type V, and go down to select lines of text.
Very quickly, the buffer gets redisplayed in a way that now lines 219
and 220 are at the beginning of the gvim window which is weird as lines
215-218 are no longer visible. This is very irritating.
Is there anything I can do to prevent this?
--
Manfred
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
When selecting text the cursor jumps in a weird way
I don't know exactly how to describe my problem.
I have started gvim and loaded a file.
The cursor goes to line 215 and the last visible lines in the gvim
window are line numbers 215 and 216.
Now I type V, and go down to select lines of text.
Very quickly, the buffer gets redisplayed in a way that now lines 219
and 220 are at the beginning of the gvim window which is weird as lines
215-218 are no longer visible. This is very irritating.
Is there anything I can do to prevent this?
--
Manfred
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I have started gvim and loaded a file.
The cursor goes to line 215 and the last visible lines in the gvim
window are line numbers 215 and 216.
Now I type V, and go down to select lines of text.
Very quickly, the buffer gets redisplayed in a way that now lines 219
and 220 are at the beginning of the gvim window which is weird as lines
215-218 are no longer visible. This is very irritating.
Is there anything I can do to prevent this?
--
Manfred
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thursday, April 25, 2019
Re: sessionoptions not restore filetype detection ??
Le jeudi 25 avril 2019 02:01:16 UTC+2, Tony Mechelynck a écrit :
> On Wed, Apr 24, 2019 at 10:43 PM <nivaemail@gmail.com> wrote:
> >
> > Le mercredi 24 avril 2019 21:18:18 UTC+2, Tony Mechelynck a écrit :
> > > On Tue, Apr 23, 2019 at 6:02 PM <nivaemail@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
> > > >
> > > > Thank you
> > > > NiVa
> > > >
> > > > " set sessionoptions=help,resize,winpos,winsize
> > >
> > > After having a look at that 'sessionoptions' setting and its many
> > > variations (none of those you set BTW, relate to filetype detection),
> > > there's nothing about filetype detection that strikes my eyes.
> > > However, ISTR that "vim -S" sources your vimrc before the session
> > > file, so any "filetype" statement in your vimrc (or, nowadays, the
> > > "filetype plugin indent on" statement in defaults.vim if you don't
> > > have a vimrc) will be executed as well. Are you the kind of person who
> > > changes filetype detection settings (to something else than what your
> > > vimrc had set) long after Vim has started, and expects them to stay
> > > that way even after a reload? Then you have a most unusual use case.
> > >
> > > Best regards,
> > > Tony.
> >
> > Hi Tony,
> >
> > What I simply notice is that when I comment on this line in my _vimrc:
> > "set sessionoptions = help, resize, winpos, winsize
> >
> > Then, the detection of file types works properly.
> >
> > When I uncomment this line, the detection of file types no longer works.
>
> That hadn't been clear to me on reading your previous post.
> >
> >
> > PS: Sorry but I did not understand everything about where you wanted to take me about the kind of person I am.
>
> Then forget it; it was due to misunderstanding what was your problem.
> >
> > PS2: I know this mksession line does not contain anything related to file type detection
>
> Now maybe this is relevant, since your 'sessionoptions' setting is
> much more restrictive than the default. If you want to find out where
> the problem (which could be a documentation problem) exactly sits, try
> adding the follwing session (sub-)options one by one to what you
> already have:
> options
> tabpages
> buffers
> blank
> folds
> curdir
> terminal
> and if by that time there is still no change, removing "winpos". If
> and when you get two settinigs differing only by one sub-option, and
> one of them restores filetype detection and the other doesn't, then
> you'll know which sub-option is responsible. This will allow you to
> propose to Bram an additional line or two somewhere between lines 6682
> and 6712 of runtime/doc/options.txt in the Vim source master.
>
>
> Best regards,
> Tony.
After doing dichotomy search tests on session options, it seems that option "buffers" was missing. This works well.
set sessionoptions=help,resize,winsize,winpos,buffers
Thank you for your help Tony!
NiVa
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Wed, Apr 24, 2019 at 10:43 PM <nivaemail@gmail.com> wrote:
> >
> > Le mercredi 24 avril 2019 21:18:18 UTC+2, Tony Mechelynck a écrit :
> > > On Tue, Apr 23, 2019 at 6:02 PM <nivaemail@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
> > > >
> > > > Thank you
> > > > NiVa
> > > >
> > > > " set sessionoptions=help,resize,winpos,winsize
> > >
> > > After having a look at that 'sessionoptions' setting and its many
> > > variations (none of those you set BTW, relate to filetype detection),
> > > there's nothing about filetype detection that strikes my eyes.
> > > However, ISTR that "vim -S" sources your vimrc before the session
> > > file, so any "filetype" statement in your vimrc (or, nowadays, the
> > > "filetype plugin indent on" statement in defaults.vim if you don't
> > > have a vimrc) will be executed as well. Are you the kind of person who
> > > changes filetype detection settings (to something else than what your
> > > vimrc had set) long after Vim has started, and expects them to stay
> > > that way even after a reload? Then you have a most unusual use case.
> > >
> > > Best regards,
> > > Tony.
> >
> > Hi Tony,
> >
> > What I simply notice is that when I comment on this line in my _vimrc:
> > "set sessionoptions = help, resize, winpos, winsize
> >
> > Then, the detection of file types works properly.
> >
> > When I uncomment this line, the detection of file types no longer works.
>
> That hadn't been clear to me on reading your previous post.
> >
> >
> > PS: Sorry but I did not understand everything about where you wanted to take me about the kind of person I am.
>
> Then forget it; it was due to misunderstanding what was your problem.
> >
> > PS2: I know this mksession line does not contain anything related to file type detection
>
> Now maybe this is relevant, since your 'sessionoptions' setting is
> much more restrictive than the default. If you want to find out where
> the problem (which could be a documentation problem) exactly sits, try
> adding the follwing session (sub-)options one by one to what you
> already have:
> options
> tabpages
> buffers
> blank
> folds
> curdir
> terminal
> and if by that time there is still no change, removing "winpos". If
> and when you get two settinigs differing only by one sub-option, and
> one of them restores filetype detection and the other doesn't, then
> you'll know which sub-option is responsible. This will allow you to
> propose to Bram an additional line or two somewhere between lines 6682
> and 6712 of runtime/doc/options.txt in the Vim source master.
>
>
> Best regards,
> Tony.
After doing dichotomy search tests on session options, it seems that option "buffers" was missing. This works well.
set sessionoptions=help,resize,winsize,winpos,buffers
Thank you for your help Tony!
NiVa
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wednesday, April 24, 2019
Re: sessionoptions not restore filetype detection ??
On Wed, Apr 24, 2019 at 10:43 PM <nivaemail@gmail.com> wrote:
>
> Le mercredi 24 avril 2019 21:18:18 UTC+2, Tony Mechelynck a écrit :
> > On Tue, Apr 23, 2019 at 6:02 PM <nivaemail@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
> > >
> > > Thank you
> > > NiVa
> > >
> > > " set sessionoptions=help,resize,winpos,winsize
> >
> > After having a look at that 'sessionoptions' setting and its many
> > variations (none of those you set BTW, relate to filetype detection),
> > there's nothing about filetype detection that strikes my eyes.
> > However, ISTR that "vim -S" sources your vimrc before the session
> > file, so any "filetype" statement in your vimrc (or, nowadays, the
> > "filetype plugin indent on" statement in defaults.vim if you don't
> > have a vimrc) will be executed as well. Are you the kind of person who
> > changes filetype detection settings (to something else than what your
> > vimrc had set) long after Vim has started, and expects them to stay
> > that way even after a reload? Then you have a most unusual use case.
> >
> > Best regards,
> > Tony.
>
> Hi Tony,
>
> What I simply notice is that when I comment on this line in my _vimrc:
> "set sessionoptions = help, resize, winpos, winsize
>
> Then, the detection of file types works properly.
>
> When I uncomment this line, the detection of file types no longer works.
That hadn't been clear to me on reading your previous post.
>
>
> PS: Sorry but I did not understand everything about where you wanted to take me about the kind of person I am.
Then forget it; it was due to misunderstanding what was your problem.
>
> PS2: I know this mksession line does not contain anything related to file type detection
Now maybe this is relevant, since your 'sessionoptions' setting is
much more restrictive than the default. If you want to find out where
the problem (which could be a documentation problem) exactly sits, try
adding the follwing session (sub-)options one by one to what you
already have:
options
tabpages
buffers
blank
folds
curdir
terminal
and if by that time there is still no change, removing "winpos". If
and when you get two settinigs differing only by one sub-option, and
one of them restores filetype detection and the other doesn't, then
you'll know which sub-option is responsible. This will allow you to
propose to Bram an additional line or two somewhere between lines 6682
and 6712 of runtime/doc/options.txt in the Vim source master.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
> Le mercredi 24 avril 2019 21:18:18 UTC+2, Tony Mechelynck a écrit :
> > On Tue, Apr 23, 2019 at 6:02 PM <nivaemail@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
> > >
> > > Thank you
> > > NiVa
> > >
> > > " set sessionoptions=help,resize,winpos,winsize
> >
> > After having a look at that 'sessionoptions' setting and its many
> > variations (none of those you set BTW, relate to filetype detection),
> > there's nothing about filetype detection that strikes my eyes.
> > However, ISTR that "vim -S" sources your vimrc before the session
> > file, so any "filetype" statement in your vimrc (or, nowadays, the
> > "filetype plugin indent on" statement in defaults.vim if you don't
> > have a vimrc) will be executed as well. Are you the kind of person who
> > changes filetype detection settings (to something else than what your
> > vimrc had set) long after Vim has started, and expects them to stay
> > that way even after a reload? Then you have a most unusual use case.
> >
> > Best regards,
> > Tony.
>
> Hi Tony,
>
> What I simply notice is that when I comment on this line in my _vimrc:
> "set sessionoptions = help, resize, winpos, winsize
>
> Then, the detection of file types works properly.
>
> When I uncomment this line, the detection of file types no longer works.
That hadn't been clear to me on reading your previous post.
>
>
> PS: Sorry but I did not understand everything about where you wanted to take me about the kind of person I am.
Then forget it; it was due to misunderstanding what was your problem.
>
> PS2: I know this mksession line does not contain anything related to file type detection
Now maybe this is relevant, since your 'sessionoptions' setting is
much more restrictive than the default. If you want to find out where
the problem (which could be a documentation problem) exactly sits, try
adding the follwing session (sub-)options one by one to what you
already have:
options
tabpages
buffers
blank
folds
curdir
terminal
and if by that time there is still no change, removing "winpos". If
and when you get two settinigs differing only by one sub-option, and
one of them restores filetype detection and the other doesn't, then
you'll know which sub-option is responsible. This will allow you to
propose to Bram an additional line or two somewhere between lines 6682
and 6712 of runtime/doc/options.txt in the Vim source master.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: sessionoptions not restore filetype detection ??
Le mercredi 24 avril 2019 21:18:18 UTC+2, Tony Mechelynck a écrit :
> On Tue, Apr 23, 2019 at 6:02 PM <nivaemail@gmail.com> wrote:
> >
> > Hi,
> >
> > Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
> >
> > Thank you
> > NiVa
> >
> > " set sessionoptions=help,resize,winpos,winsize
>
> After having a look at that 'sessionoptions' setting and its many
> variations (none of those you set BTW, relate to filetype detection),
> there's nothing about filetype detection that strikes my eyes.
> However, ISTR that "vim -S" sources your vimrc before the session
> file, so any "filetype" statement in your vimrc (or, nowadays, the
> "filetype plugin indent on" statement in defaults.vim if you don't
> have a vimrc) will be executed as well. Are you the kind of person who
> changes filetype detection settings (to something else than what your
> vimrc had set) long after Vim has started, and expects them to stay
> that way even after a reload? Then you have a most unusual use case.
>
> Best regards,
> Tony.
Hi Tony,
What I simply notice is that when I comment on this line in my _vimrc:
"set sessionoptions = help, resize, winpos, winsize
Then, the detection of file types works properly.
When I uncomment this line, the detection of file types no longer works.
PS: Sorry but I did not understand everything about where you wanted to take me about the kind of person I am.
PS2: I know this mksession line does not contain anything related to file type detection
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Tue, Apr 23, 2019 at 6:02 PM <nivaemail@gmail.com> wrote:
> >
> > Hi,
> >
> > Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
> >
> > Thank you
> > NiVa
> >
> > " set sessionoptions=help,resize,winpos,winsize
>
> After having a look at that 'sessionoptions' setting and its many
> variations (none of those you set BTW, relate to filetype detection),
> there's nothing about filetype detection that strikes my eyes.
> However, ISTR that "vim -S" sources your vimrc before the session
> file, so any "filetype" statement in your vimrc (or, nowadays, the
> "filetype plugin indent on" statement in defaults.vim if you don't
> have a vimrc) will be executed as well. Are you the kind of person who
> changes filetype detection settings (to something else than what your
> vimrc had set) long after Vim has started, and expects them to stay
> that way even after a reload? Then you have a most unusual use case.
>
> Best regards,
> Tony.
Hi Tony,
What I simply notice is that when I comment on this line in my _vimrc:
"set sessionoptions = help, resize, winpos, winsize
Then, the detection of file types works properly.
When I uncomment this line, the detection of file types no longer works.
PS: Sorry but I did not understand everything about where you wanted to take me about the kind of person I am.
PS2: I know this mksession line does not contain anything related to file type detection
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: sessionoptions not restore filetype detection ??
On Tue, Apr 23, 2019 at 6:02 PM <nivaemail@gmail.com> wrote:
>
> Hi,
>
> Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
>
> Thank you
> NiVa
>
> " set sessionoptions=help,resize,winpos,winsize
After having a look at that 'sessionoptions' setting and its many
variations (none of those you set BTW, relate to filetype detection),
there's nothing about filetype detection that strikes my eyes.
However, ISTR that "vim -S" sources your vimrc before the session
file, so any "filetype" statement in your vimrc (or, nowadays, the
"filetype plugin indent on" statement in defaults.vim if you don't
have a vimrc) will be executed as well. Are you the kind of person who
changes filetype detection settings (to something else than what your
vimrc had set) long after Vim has started, and expects them to stay
that way even after a reload? Then you have a most unusual use case.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
> Hi,
>
> Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
>
> Thank you
> NiVa
>
> " set sessionoptions=help,resize,winpos,winsize
After having a look at that 'sessionoptions' setting and its many
variations (none of those you set BTW, relate to filetype detection),
there's nothing about filetype detection that strikes my eyes.
However, ISTR that "vim -S" sources your vimrc before the session
file, so any "filetype" statement in your vimrc (or, nowadays, the
"filetype plugin indent on" statement in defaults.vim if you don't
have a vimrc) will be executed as well. Are you the kind of person who
changes filetype detection settings (to something else than what your
vimrc had set) long after Vim has started, and expects them to stay
that way even after a reload? Then you have a most unusual use case.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tuesday, April 23, 2019
Re: Personal syntax highligth for ToDo and else.
ok thanks
On Tue, 2019-04-23 at 11:18 -0400, Marvin Renich wrote:
> * white-wolf <white-wolf@ovh.fr> [190423 04:25]:
> > hi,
> > i use txt to organize my ToDo, my AdresseBook en else.
> > i would like to colorize my txt by a personnal syntax hightlight.
> >
> > how can do ?
>
> In addition to the other good answers, if you want to write your own,
> try «:help syntax» which has all the reference information
> needed. That
> help file, in its overview, also points to two sections in the User
> Manual with more tutorial-oriented help.
>
> ...Marvin
>
> --
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Tue, 2019-04-23 at 11:18 -0400, Marvin Renich wrote:
> * white-wolf <white-wolf@ovh.fr> [190423 04:25]:
> > hi,
> > i use txt to organize my ToDo, my AdresseBook en else.
> > i would like to colorize my txt by a personnal syntax hightlight.
> >
> > how can do ?
>
> In addition to the other good answers, if you want to write your own,
> try «:help syntax» which has all the reference information
> needed. That
> help file, in its overview, also points to two sections in the User
> Manual with more tutorial-oriented help.
>
> ...Marvin
>
> --
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
sessionoptions not restore filetype detection ??
Hi,
Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
Thank you
NiVa
" set sessionoptions=help,resize,winpos,winsize
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Using mksession file and these sessionoptions, I don't see why vim does not restore filetype detection after reloading .vim files for example.
Thank you
NiVa
" set sessionoptions=help,resize,winpos,winsize
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Personal syntax highligth for ToDo and else.
* white-wolf <white-wolf@ovh.fr> [190423 04:25]:
> hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
>
> how can do ?
In addition to the other good answers, if you want to write your own,
try «:help syntax» which has all the reference information needed. That
help file, in its overview, also points to two sections in the User
Manual with more tutorial-oriented help.
...Marvin
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
>
> how can do ?
In addition to the other good answers, if you want to write your own,
try «:help syntax» which has all the reference information needed. That
help file, in its overview, also points to two sections in the User
Manual with more tutorial-oriented help.
...Marvin
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Personal syntax highligth for ToDo and else.
* white-wolf <white-wolf@ovh.fr> [190423 04:25]:
> hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
>
> how can do ?
In addition to the other good answers, if you want to write your own,
try «:help syntax» which has all the reference information needed. That
help file, in its overview, also points to two sections in the User
Manual with more tutorial-oriented help.
...Marvin
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
>
> how can do ?
In addition to the other good answers, if you want to write your own,
try «:help syntax» which has all the reference information needed. That
help file, in its overview, also points to two sections in the User
Manual with more tutorial-oriented help.
...Marvin
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Personal syntax highligth for ToDo and else.
sorry it's no corresponding that i find.
i have personnal presentation, and i would like print for evry day to
paste on my book en valide with coche...
it's a repetitive ToDo for evry day.
and for else ToDo, i have my personal presentation : eg.
[ ]--> some one
[ ]--> some else
\___ some other
\___ some else other
with category and title...
BR
WW
On Tue, 2019-04-23 at 10:39 +0200, Magnus Woldrich wrote:
> On 4/23/19, white-wolf <white-wolf@ovh.fr> wrote:
> > hi,
>
> Hi,
>
> > i use txt to organize my ToDo, my AdresseBook en else.
> > i would like to colorize my txt by a personnal syntax hightlight.
>
> It's quite simple. I've made a personal todo and a personal
> work-related syntax file:
> https://github.com/trapd00r/vim-syntax-todo
> https://github.com/trapd00r/vim-syntax-tidningsbud
>
> might give you a head start.
>
> --
> Magnus Woldrich
> japh@freenode
> http://japh.se
> https://github.com/trapd00r
>
> --
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
i have personnal presentation, and i would like print for evry day to
paste on my book en valide with coche...
it's a repetitive ToDo for evry day.
and for else ToDo, i have my personal presentation : eg.
[ ]--> some one
[ ]--> some else
\___ some other
\___ some else other
with category and title...
BR
WW
On Tue, 2019-04-23 at 10:39 +0200, Magnus Woldrich wrote:
> On 4/23/19, white-wolf <white-wolf@ovh.fr> wrote:
> > hi,
>
> Hi,
>
> > i use txt to organize my ToDo, my AdresseBook en else.
> > i would like to colorize my txt by a personnal syntax hightlight.
>
> It's quite simple. I've made a personal todo and a personal
> work-related syntax file:
> https://github.com/trapd00r/vim-syntax-todo
> https://github.com/trapd00r/vim-syntax-tidningsbud
>
> might give you a head start.
>
> --
> Magnus Woldrich
> japh@freenode
> http://japh.se
> https://github.com/trapd00r
>
> --
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Personal syntax highligth for ToDo and else.
On Tue, 23 Apr 2019 00:12:21 +0200
white-wolf <white-wolf@ovh.fr> wrote:
> hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
>
Hi,
perhaps see https://github.com/aaronbieber/vim-quicktask and also
https://www.shlomifish.org/meta/FAQ/#todo_lists_and_organised .
Regards,
Shlomi
> how can do ?
>
> Best Regard,
> Wolf.
>
--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
My Aphorisms - http://www.shlomifish.org/humour.html
When Chuck Norris receives an E-mail signed "Sent from my iPhone", he makes
sure that iPhone won't be able to send any more E-mails — to Norris or
otherwise.
— http://www.shlomifish.org/humour/bits/facts/Chuck-Norris/
Please reply to list if it's a mailing list post - http://shlom.in/reply .
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
white-wolf <white-wolf@ovh.fr> wrote:
> hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
>
Hi,
perhaps see https://github.com/aaronbieber/vim-quicktask and also
https://www.shlomifish.org/meta/FAQ/#todo_lists_and_organised .
Regards,
Shlomi
> how can do ?
>
> Best Regard,
> Wolf.
>
--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
My Aphorisms - http://www.shlomifish.org/humour.html
When Chuck Norris receives an E-mail signed "Sent from my iPhone", he makes
sure that iPhone won't be able to send any more E-mails — to Norris or
otherwise.
— http://www.shlomifish.org/humour/bits/facts/Chuck-Norris/
Please reply to list if it's a mailing list post - http://shlom.in/reply .
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Personal syntax highligth for ToDo and else.
On 4/23/19, white-wolf <white-wolf@ovh.fr> wrote:
> hi,
Hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
It's quite simple. I've made a personal todo and a personal
work-related syntax file:
https://github.com/trapd00r/vim-syntax-todo
https://github.com/trapd00r/vim-syntax-tidningsbud
might give you a head start.
--
Magnus Woldrich
japh@freenode
http://japh.se
https://github.com/trapd00r
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> hi,
Hi,
> i use txt to organize my ToDo, my AdresseBook en else.
> i would like to colorize my txt by a personnal syntax hightlight.
It's quite simple. I've made a personal todo and a personal
work-related syntax file:
https://github.com/trapd00r/vim-syntax-todo
https://github.com/trapd00r/vim-syntax-tidningsbud
might give you a head start.
--
Magnus Woldrich
japh@freenode
http://japh.se
https://github.com/trapd00r
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Monday, April 22, 2019
Personal syntax highligth for ToDo and else.
hi,
i use txt to organize my ToDo, my AdresseBook en else.
i would like to colorize my txt by a personnal syntax hightlight.
how can do ?
Best Regard,
Wolf.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
i use txt to organize my ToDo, my AdresseBook en else.
i would like to colorize my txt by a personnal syntax hightlight.
how can do ?
Best Regard,
Wolf.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Saturday, April 20, 2019
Re: colorscheme 16-bit
On Fri, Apr 19, 2019 at 08:52:29PM +0200, meine wrote:
> on how to adapt a vim colorscheme to 16-bits color
Thank all for your replies and reading!
@Salman: you have an interesting option to keep up with developments!
@Frank: TNX for the nickel! My main box has a Nvidia card and I chose
not to use it and stick with the basic `sh' terminal in FreeBSD 12.
Tried the `fish' shell but that didn't give me extra colors, so I'll
have to stick with the basic 16-bits of colors...
@Tony: TNX for your extensive reply! IMHO vim is not only for rescueing
your system. I preferrably use vim in a tty console, because working in
that environment skips all the nuisance and distraction my X11
environment has -- no temptation to get a quick view of mastodon,
twitter or the headlines. When in GUI, I still prefer using vim in an xterm
window, but when I double-click a file in the XFE file manager gvim does
the job.
Have a nice Easter Weekend,
BFN
//meine
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> on how to adapt a vim colorscheme to 16-bits color
Thank all for your replies and reading!
@Salman: you have an interesting option to keep up with developments!
@Frank: TNX for the nickel! My main box has a Nvidia card and I chose
not to use it and stick with the basic `sh' terminal in FreeBSD 12.
Tried the `fish' shell but that didn't give me extra colors, so I'll
have to stick with the basic 16-bits of colors...
@Tony: TNX for your extensive reply! IMHO vim is not only for rescueing
your system. I preferrably use vim in a tty console, because working in
that environment skips all the nuisance and distraction my X11
environment has -- no temptation to get a quick view of mastodon,
twitter or the headlines. When in GUI, I still prefer using vim in an xterm
window, but when I double-click a file in the XFE file manager gvim does
the job.
Have a nice Easter Weekend,
BFN
//meine
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Friday, April 19, 2019
Re: colorscheme 16-bit
The problem is that too many colorschemes these days are not
cterm-conscious: they assume that you have a lot of colours at your
disposal and sometimes even that you are using gvim — and yet, Vim, as
an editor, is still extremely useful for some tasks that have to be
done with no GUI interface; one of these tasks would be rescuing a
failed software upgrade, where you can't rely on a functioning X11
server: then you are left with the "bare bones" console which usually
has only 8 background and 16 foreground colors, and uses the cterm=
ctermbg= ctermfg= settings of the :hi command, not the gui= guibg=
guifg= guisp= settings. Another such task would be tweaking settings
on a server where no X11 package is installed (and usually no screen
or keyboard either but the sysadmin added them for the occasion).
IMHO Vim's default colors are quite good, though not perfect (nothing
is perfect) for both cterm and gui (I haven't had the occasion to test
the term= colors for lack of the necessary monochrome-terminal
hardware in the days since I've known Vim) so I use an owncoded
colorscheme which defines only what I regard as insufficient in the
default colors (and no shame on Bram: de coloribus non est
disputandum). When running Console Vim in a terminal which is capable
of 256 colors (such as konsole or xterm) I supplement this colorscheme
(which you'll find attached; feel free to use it or not, and if you
do, to adapt it to your own use case; if you want to try it, its home
is in ~/.vim/colors on a Unix-like system, or in ~/vimfiles/colors on
a Windows system) with the CSApprox plugin (available at vim.org), so
in that case I get the same colors, or as close as possible and almost
indistinguishable to my eye, in Vim in konsole or xterm and in gvim.
(I wrote that colorscheme before the 'termguicolors' option was
available and this way I don't depend on the +termguicolors feature
being compiled-in.) Of course, in the 8/16 bare-bones console (where
CSApprox detects that &t_Co < 88 and disables itself) the colors are
very different but at least they are distinct.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
cterm-conscious: they assume that you have a lot of colours at your
disposal and sometimes even that you are using gvim — and yet, Vim, as
an editor, is still extremely useful for some tasks that have to be
done with no GUI interface; one of these tasks would be rescuing a
failed software upgrade, where you can't rely on a functioning X11
server: then you are left with the "bare bones" console which usually
has only 8 background and 16 foreground colors, and uses the cterm=
ctermbg= ctermfg= settings of the :hi command, not the gui= guibg=
guifg= guisp= settings. Another such task would be tweaking settings
on a server where no X11 package is installed (and usually no screen
or keyboard either but the sysadmin added them for the occasion).
IMHO Vim's default colors are quite good, though not perfect (nothing
is perfect) for both cterm and gui (I haven't had the occasion to test
the term= colors for lack of the necessary monochrome-terminal
hardware in the days since I've known Vim) so I use an owncoded
colorscheme which defines only what I regard as insufficient in the
default colors (and no shame on Bram: de coloribus non est
disputandum). When running Console Vim in a terminal which is capable
of 256 colors (such as konsole or xterm) I supplement this colorscheme
(which you'll find attached; feel free to use it or not, and if you
do, to adapt it to your own use case; if you want to try it, its home
is in ~/.vim/colors on a Unix-like system, or in ~/vimfiles/colors on
a Windows system) with the CSApprox plugin (available at vim.org), so
in that case I get the same colors, or as close as possible and almost
indistinguishable to my eye, in Vim in konsole or xterm and in gvim.
(I wrote that colorscheme before the 'termguicolors' option was
available and this way I don't depend on the +termguicolors feature
being compiled-in.) Of course, in the 8/16 bare-bones console (where
CSApprox detects that &t_Co < 88 and disables itself) the colors are
very different but at least they are distinct.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: colorscheme 16-bit
Here's a nickel, kid. Get yourself a better console:
https://www.freebsd.org/cgi/man.cgi?query=vt&apropos=0&sektion=4&manpath=FreeBSD+12.0-RELEASE+and+Ports&arch=default&format=html
;-)
On Fri, 19 Apr 2019 at 19:52, meine <trialero@gmx.com> wrote:
>
> Hi,
>
> There are lot of great Vim colorschemes out there, but beware to use
> one in a plain tty console -- it looks like nothing. Recently I adopted
> switching relative and absolute line numbers, and that is where coloring
> is important. In console most of us probably use a more basic
> colorscheme, avoiding all the soft focus and tones that won't
> display anyway.
>
> Although most colorschemes in eg. vimcolors.org have a button to select
> `Term' savvy schemes, almost all of them are 256 colors and not the 8 or
> max 16 colors you have in a decent tty console. `Term' isn't the same as
> a plain console without GUI.
>
> This afternoon I did the following (to end frustration ;-):
>
> 1. download the colorscheme you like most, and put it in ~/.vim/colors/
> Open the file in your preferred editor, and use it with `:color <myscheme>'
>
> 2. look for the lines with the parts that most annoy you in console. For
> me it was LineNr, Comment and CursorLineNr. The first two where too dark
> and the last one I wanted yellow instead of white (nighted.vim
> scheme);
>
> 3. change the value of `ctermfg' to a 16-bit value that actually works.
> Leave the rest that is fine; Search the Net for a `256colors2.pl' Perl
> file that gives your console color numbers (top row 0-7, bottom row
> 8-15);
>
> 4. save (as) the changed colorscheme under the same name with eg. `_16b' on
> the end to mark your changes;
>
> 5. test your adapted colorscheme with `:color <myscheme>_16b' and
> evaluate your changes. Don't forget to change the naming of the
> colorscheme in the top lines of the <myscheme>_16b.vim file: `let
> g:colors_name = <newname_with_16b>'. This is improtant for proper
> working in your `vimrc';
>
> 6. if it works, just add your `_16b' scheme to your .vimrc.
>
> For me it works!
>
> Happy Easter Weekend!
>
> //meine
>
> --
> --
> You received this message from the "vim_use" 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 Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Frank
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
https://www.freebsd.org/cgi/man.cgi?query=vt&apropos=0&sektion=4&manpath=FreeBSD+12.0-RELEASE+and+Ports&arch=default&format=html
;-)
On Fri, 19 Apr 2019 at 19:52, meine <trialero@gmx.com> wrote:
>
> Hi,
>
> There are lot of great Vim colorschemes out there, but beware to use
> one in a plain tty console -- it looks like nothing. Recently I adopted
> switching relative and absolute line numbers, and that is where coloring
> is important. In console most of us probably use a more basic
> colorscheme, avoiding all the soft focus and tones that won't
> display anyway.
>
> Although most colorschemes in eg. vimcolors.org have a button to select
> `Term' savvy schemes, almost all of them are 256 colors and not the 8 or
> max 16 colors you have in a decent tty console. `Term' isn't the same as
> a plain console without GUI.
>
> This afternoon I did the following (to end frustration ;-):
>
> 1. download the colorscheme you like most, and put it in ~/.vim/colors/
> Open the file in your preferred editor, and use it with `:color <myscheme>'
>
> 2. look for the lines with the parts that most annoy you in console. For
> me it was LineNr, Comment and CursorLineNr. The first two where too dark
> and the last one I wanted yellow instead of white (nighted.vim
> scheme);
>
> 3. change the value of `ctermfg' to a 16-bit value that actually works.
> Leave the rest that is fine; Search the Net for a `256colors2.pl' Perl
> file that gives your console color numbers (top row 0-7, bottom row
> 8-15);
>
> 4. save (as) the changed colorscheme under the same name with eg. `_16b' on
> the end to mark your changes;
>
> 5. test your adapted colorscheme with `:color <myscheme>_16b' and
> evaluate your changes. Don't forget to change the naming of the
> colorscheme in the top lines of the <myscheme>_16b.vim file: `let
> g:colors_name = <newname_with_16b>'. This is improtant for proper
> working in your `vimrc';
>
> 6. if it works, just add your `_16b' scheme to your .vimrc.
>
> For me it works!
>
> Happy Easter Weekend!
>
> //meine
>
> --
> --
> You received this message from the "vim_use" 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 Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Frank
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: colorscheme 16-bit
I always worry that some day there will be a newer version of a color scheme file and I'll lose fancy new colours this way. My solution is to create a custom file (such as mysolarized.vim) and source the original in there and just change the name and replace those colors that I want changed.
I've gone pretty far with this and have a mycommon.vim and mycommonlight.vim and mycommondark.vim that I source from all my versions, the latter two depending on the value of &background.
--
Salman
Salman
On Fri, Apr 19, 2019, 14:52 meine <trialero@gmx.com> wrote:
Hi,
There are lot of great Vim colorschemes out there, but beware to use
one in a plain tty console -- it looks like nothing. Recently I adopted
switching relative and absolute line numbers, and that is where coloring
is important. In console most of us probably use a more basic
colorscheme, avoiding all the soft focus and tones that won't
display anyway.
Although most colorschemes in eg. vimcolors.org have a button to select
`Term' savvy schemes, almost all of them are 256 colors and not the 8 or
max 16 colors you have in a decent tty console. `Term' isn't the same as
a plain console without GUI.
This afternoon I did the following (to end frustration ;-):
1. download the colorscheme you like most, and put it in ~/.vim/colors/
Open the file in your preferred editor, and use it with `:color <myscheme>'
2. look for the lines with the parts that most annoy you in console. For
me it was LineNr, Comment and CursorLineNr. The first two where too dark
and the last one I wanted yellow instead of white (nighted.vim
scheme);
3. change the value of `ctermfg' to a 16-bit value that actually works.
Leave the rest that is fine; Search the Net for a `256colors2.pl' Perl
file that gives your console color numbers (top row 0-7, bottom row
8-15);
4. save (as) the changed colorscheme under the same name with eg. `_16b' on
the end to mark your changes;
5. test your adapted colorscheme with `:color <myscheme>_16b' and
evaluate your changes. Don't forget to change the naming of the
colorscheme in the top lines of the <myscheme>_16b.vim file: `let
g:colors_name = <newname_with_16b>'. This is improtant for proper
working in your `vimrc';
6. if it works, just add your `_16b' scheme to your .vimrc.
For me it works!
Happy Easter Weekend!
//meine
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
colorscheme 16-bit
Hi,
There are lot of great Vim colorschemes out there, but beware to use
one in a plain tty console -- it looks like nothing. Recently I adopted
switching relative and absolute line numbers, and that is where coloring
is important. In console most of us probably use a more basic
colorscheme, avoiding all the soft focus and tones that won't
display anyway.
Although most colorschemes in eg. vimcolors.org have a button to select
`Term' savvy schemes, almost all of them are 256 colors and not the 8 or
max 16 colors you have in a decent tty console. `Term' isn't the same as
a plain console without GUI.
This afternoon I did the following (to end frustration ;-):
1. download the colorscheme you like most, and put it in ~/.vim/colors/
Open the file in your preferred editor, and use it with `:color <myscheme>'
2. look for the lines with the parts that most annoy you in console. For
me it was LineNr, Comment and CursorLineNr. The first two where too dark
and the last one I wanted yellow instead of white (nighted.vim
scheme);
3. change the value of `ctermfg' to a 16-bit value that actually works.
Leave the rest that is fine; Search the Net for a `256colors2.pl' Perl
file that gives your console color numbers (top row 0-7, bottom row
8-15);
4. save (as) the changed colorscheme under the same name with eg. `_16b' on
the end to mark your changes;
5. test your adapted colorscheme with `:color <myscheme>_16b' and
evaluate your changes. Don't forget to change the naming of the
colorscheme in the top lines of the <myscheme>_16b.vim file: `let
g:colors_name = <newname_with_16b>'. This is improtant for proper
working in your `vimrc';
6. if it works, just add your `_16b' scheme to your .vimrc.
For me it works!
Happy Easter Weekend!
//meine
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
There are lot of great Vim colorschemes out there, but beware to use
one in a plain tty console -- it looks like nothing. Recently I adopted
switching relative and absolute line numbers, and that is where coloring
is important. In console most of us probably use a more basic
colorscheme, avoiding all the soft focus and tones that won't
display anyway.
Although most colorschemes in eg. vimcolors.org have a button to select
`Term' savvy schemes, almost all of them are 256 colors and not the 8 or
max 16 colors you have in a decent tty console. `Term' isn't the same as
a plain console without GUI.
This afternoon I did the following (to end frustration ;-):
1. download the colorscheme you like most, and put it in ~/.vim/colors/
Open the file in your preferred editor, and use it with `:color <myscheme>'
2. look for the lines with the parts that most annoy you in console. For
me it was LineNr, Comment and CursorLineNr. The first two where too dark
and the last one I wanted yellow instead of white (nighted.vim
scheme);
3. change the value of `ctermfg' to a 16-bit value that actually works.
Leave the rest that is fine; Search the Net for a `256colors2.pl' Perl
file that gives your console color numbers (top row 0-7, bottom row
8-15);
4. save (as) the changed colorscheme under the same name with eg. `_16b' on
the end to mark your changes;
5. test your adapted colorscheme with `:color <myscheme>_16b' and
evaluate your changes. Don't forget to change the naming of the
colorscheme in the top lines of the <myscheme>_16b.vim file: `let
g:colors_name = <newname_with_16b>'. This is improtant for proper
working in your `vimrc';
6. if it works, just add your `_16b' scheme to your .vimrc.
For me it works!
Happy Easter Weekend!
//meine
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tuesday, April 16, 2019
Re: Vim visual selection underlined
On Tuesday, April 16, 2019 at 8:14:27 AM UTC+1, Jeenu wrote:
> Hi,
>
> Normally, Vim visual selection is displayed terminal reverse color.
> Sometimes I find that, after attaching to a perviously-detached
> terminal session (tmux, screen, etc.), the visual selection is
> displayed as bold underlines. See this question for example:
> https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
>
> The only solution I've found is to quit Vim, which I want to avoid.
>
> Any ideas for troubleshooting this issue?
>
> Thanks.
>
> --
> Jeenu
Please ignore. This was sent a week ago from my email address. I posted directly on the group; see https://groups.google.com/forum/#!topic/vim_use/QNuq7_s6P9A.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Hi,
>
> Normally, Vim visual selection is displayed terminal reverse color.
> Sometimes I find that, after attaching to a perviously-detached
> terminal session (tmux, screen, etc.), the visual selection is
> displayed as bold underlines. See this question for example:
> https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
>
> The only solution I've found is to quit Vim, which I want to avoid.
>
> Any ideas for troubleshooting this issue?
>
> Thanks.
>
> --
> Jeenu
Please ignore. This was sent a week ago from my email address. I posted directly on the group; see https://groups.google.com/forum/#!topic/vim_use/QNuq7_s6P9A.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Monday, April 15, 2019
Re: Vim selection underlined rather than reversed
On Monday, April 15, 2019 at 8:25:39 PM UTC+1, Tony Mechelynck wrote:
> On Mon, Apr 15, 2019 at 9:00 PM Jeenu wrote:
> >
> > On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > > >
> > > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > > >
> > > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > > >
> > > > Thanks,
> > > > Jeenu
> > >
> > > I don't know why it happens but I know how to find out: next time the
> > > problem happens, and after making sure Vim is in Normal mode (this
> > > will usually mean hitting <Esc>, which will clear the Visual
> > > highlighting) type
> > >
> > > :verbose hi Visual
> >
> > I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
> >
> > Also, both sessions say background is dark.
> >
> > Not sure what to make of these.
> >
> > Jeenu
> >
>
> The right-hand screenshot (with underlining) shows that the highlight
> was set by the "desert" colorscheme.
>
> :colors default
>
> will clear that.
Switching color scheme didn't have any effect, if that's what you were suggesting.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Mon, Apr 15, 2019 at 9:00 PM Jeenu wrote:
> >
> > On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > > >
> > > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > > >
> > > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > > >
> > > > Thanks,
> > > > Jeenu
> > >
> > > I don't know why it happens but I know how to find out: next time the
> > > problem happens, and after making sure Vim is in Normal mode (this
> > > will usually mean hitting <Esc>, which will clear the Visual
> > > highlighting) type
> > >
> > > :verbose hi Visual
> >
> > I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
> >
> > Also, both sessions say background is dark.
> >
> > Not sure what to make of these.
> >
> > Jeenu
> >
>
> The right-hand screenshot (with underlining) shows that the highlight
> was set by the "desert" colorscheme.
>
> :colors default
>
> will clear that.
Switching color scheme didn't have any effect, if that's what you were suggesting.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
On Monday, April 15, 2019 at 8:15:19 PM UTC+1, Christian Brabandt wrote:
> On Mo, 15 Apr 2019, Jeenu wrote:
>
> > On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > > >
> > > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > > >
> > > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > > >
> > > > Thanks,
> > > > Jeenu
> > >
> > > I don't know why it happens but I know how to find out: next time the
> > > problem happens, and after making sure Vim is in Normal mode (this
> > > will usually mean hitting <Esc>, which will clear the Visual
> > > highlighting) type
> > >
> > > :verbose hi Visual
> >
> > I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
> >
> > Also, both sessions say background is dark.
> >
> > Not sure what to make of these.
>
> Please show the text output.
:verbose hi Visual
Visual xxx term=reverse cterm=reverse ctermbg=242 guifg=khaki guibg=olivedrab
Last set from /usr/share/vim/vim74/colors/desert.vim
Press ENTER or type command to continue
> Another thing that is likely to be the cause is, Vim is using the
> VisualNOS highlighting group. This is used, when Vim cannot connect to
> the X Server. You mentioned using tmux and re-attaching sessions, so my
> guess is, the re-attachment made Vim not correctly reset the X connect.
>
> So the different highlighting is a way to let you know of it.
>
> There was an issue about Vim not correctly resetting up the X
> connection, (I believe #3649) and a fix seems to have been included by
> 8.1.0615.
The Cygwin server I'm running on my Windows host (vim runs on a remote Linux host) did restart, so could be that issue.
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Mo, 15 Apr 2019, Jeenu wrote:
>
> > On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > > >
> > > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > > >
> > > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > > >
> > > > Thanks,
> > > > Jeenu
> > >
> > > I don't know why it happens but I know how to find out: next time the
> > > problem happens, and after making sure Vim is in Normal mode (this
> > > will usually mean hitting <Esc>, which will clear the Visual
> > > highlighting) type
> > >
> > > :verbose hi Visual
> >
> > I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
> >
> > Also, both sessions say background is dark.
> >
> > Not sure what to make of these.
>
> Please show the text output.
:verbose hi Visual
Visual xxx term=reverse cterm=reverse ctermbg=242 guifg=khaki guibg=olivedrab
Last set from /usr/share/vim/vim74/colors/desert.vim
Press ENTER or type command to continue
> Another thing that is likely to be the cause is, Vim is using the
> VisualNOS highlighting group. This is used, when Vim cannot connect to
> the X Server. You mentioned using tmux and re-attaching sessions, so my
> guess is, the re-attachment made Vim not correctly reset the X connect.
>
> So the different highlighting is a way to let you know of it.
>
> There was an issue about Vim not correctly resetting up the X
> connection, (I believe #3649) and a fix seems to have been included by
> 8.1.0615.
The Cygwin server I'm running on my Windows host (vim runs on a remote Linux host) did restart, so could be that issue.
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
On Mon, Apr 15, 2019 at 9:00 PM Jeenu <jeenuv@gmail.com> wrote:
>
> On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > >
> > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > >
> > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > >
> > > Thanks,
> > > Jeenu
> >
> > I don't know why it happens but I know how to find out: next time the
> > problem happens, and after making sure Vim is in Normal mode (this
> > will usually mean hitting <Esc>, which will clear the Visual
> > highlighting) type
> >
> > :verbose hi Visual
>
> I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
>
> Also, both sessions say background is dark.
>
> Not sure what to make of these.
>
> Jeenu
>
The right-hand screenshot (with underlining) shows that the highlight
was set by the "desert" colorscheme.
:colors default
will clear that.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
> On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > >
> > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > >
> > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > >
> > > Thanks,
> > > Jeenu
> >
> > I don't know why it happens but I know how to find out: next time the
> > problem happens, and after making sure Vim is in Normal mode (this
> > will usually mean hitting <Esc>, which will clear the Visual
> > highlighting) type
> >
> > :verbose hi Visual
>
> I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
>
> Also, both sessions say background is dark.
>
> Not sure what to make of these.
>
> Jeenu
>
The right-hand screenshot (with underlining) shows that the highlight
was set by the "desert" colorscheme.
:colors default
will clear that.
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
On Mo, 15 Apr 2019, Jeenu wrote:
> On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > >
> > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > >
> > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > >
> > > Thanks,
> > > Jeenu
> >
> > I don't know why it happens but I know how to find out: next time the
> > problem happens, and after making sure Vim is in Normal mode (this
> > will usually mean hitting <Esc>, which will clear the Visual
> > highlighting) type
> >
> > :verbose hi Visual
>
> I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
>
> Also, both sessions say background is dark.
>
> Not sure what to make of these.
Please show the text output.
Another thing that is likely to be the cause is, Vim is using the
VisualNOS highlighting group. This is used, when Vim cannot connect to
the X Server. You mentioned using tmux and re-attaching sessions, so my
guess is, the re-attachment made Vim not correctly reset the X connect.
So the different highlighting is a way to let you know of it.
There was an issue about Vim not correctly resetting up the X
connection, (I believe #3649) and a fix seems to have been included by
8.1.0615.
Best,
Christian
--
Mir willst du zum Gotte machen
Solch ein Jammerbild am Holze!
-- Johann Wolfgang von Goethe
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > >
> > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > >
> > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > >
> > > Thanks,
> > > Jeenu
> >
> > I don't know why it happens but I know how to find out: next time the
> > problem happens, and after making sure Vim is in Normal mode (this
> > will usually mean hitting <Esc>, which will clear the Visual
> > highlighting) type
> >
> > :verbose hi Visual
>
> I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
>
> Also, both sessions say background is dark.
>
> Not sure what to make of these.
Please show the text output.
Another thing that is likely to be the cause is, Vim is using the
VisualNOS highlighting group. This is used, when Vim cannot connect to
the X Server. You mentioned using tmux and re-attaching sessions, so my
guess is, the re-attachment made Vim not correctly reset the X connect.
So the different highlighting is a way to let you know of it.
There was an issue about Vim not correctly resetting up the X
connection, (I believe #3649) and a fix seems to have been included by
8.1.0615.
Best,
Christian
--
Mir willst du zum Gotte machen
Solch ein Jammerbild am Holze!
-- Johann Wolfgang von Goethe
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
> On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> >
> > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> >
> > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> >
> > Thanks,
> > Jeenu
>
> I don't know why it happens but I know how to find out: next time the
> problem happens, and after making sure Vim is in Normal mode (this
> will usually mean hitting <Esc>, which will clear the Visual
> highlighting) type
>
> :verbose hi Visual
I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
Also, both sessions say background is dark.
Not sure what to make of these.
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
On 4/15/19 9:24 AM, Jeenu wrote:
> Sometimes, after I attach to a tmux session, visual selection in
> an already-running vim instance is shown as underlined instead of
> reversed. See the attached files for the difference; both are from the
> same host - one from new, and the other from existing session. The only
> way out I've found is to quit and launch vim again. Does any one know
> why this happens and/or how to fix it?
This sounds to me like screen is loosing state and not (re)displaying
things properly after some condition.
I would bet another order of magnitude that this is the case if you
visually select something so it's highlighted, change screen (disconnect
/ switch screens), change screen back (reconnect / switch back), and
what was highlighted is now underlined.
> This is the same problem as someone had posted a while ago:
> https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
This seems to have the same symptoms to me.
You can probably test vim, if not eliminate it from the scenario, by
playing with ANSI control codes at a command line and see if the
symptoms are the same as vim when changing screen (see above).
--
Grant. . . .
unix || die
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Sometimes, after I attach to a tmux session, visual selection in
> an already-running vim instance is shown as underlined instead of
> reversed. See the attached files for the difference; both are from the
> same host - one from new, and the other from existing session. The only
> way out I've found is to quit and launch vim again. Does any one know
> why this happens and/or how to fix it?
This sounds to me like screen is loosing state and not (re)displaying
things properly after some condition.
I would bet another order of magnitude that this is the case if you
visually select something so it's highlighted, change screen (disconnect
/ switch screens), change screen back (reconnect / switch back), and
what was highlighted is now underlined.
> This is the same problem as someone had posted a while ago:
> https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
This seems to have the same symptoms to me.
You can probably test vim, if not eliminate it from the scenario, by
playing with ANSI control codes at a command line and see if the
symptoms are the same as vim when changing screen (see above).
--
Grant. . . .
unix || die
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim selection underlined rather than reversed
On Mon, Apr 15, 2019 at 5:24 PM Jeenu <jeenuv@gmail.com> wrote:
>
> Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
>
> This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
>
> Thanks,
> Jeenu
I don't know why it happens but I know how to find out: next time the
problem happens, and after making sure Vim is in Normal mode (this
will usually mean hitting <Esc>, which will clear the Visual
highlighting) type
:verbose hi Visual
followed by <Enter>. Vim will answer by telling you not only exactly
what the Visual highlight is now set to, but also, which line of which
script (if any) last changed it. The script name and line can only be
missing if that highlight is either at its default, or was last set
manually.
Another possibly relevant setting is the 'background' setting, which
may be "dark" or "light" (without the quotes) and defines whether Vim
thinks that your current default background is a dark one or a bright
one respectively.
:verbose set bg
will tell you the current value and which script (if any) last set it.
Here it is more likely that no script will be mentioned, meaning the
value is still the default value (which, in Console Vim, can be either
"light" or "dark" depending on what Vim believes that you were using
immediately before startup; in gvim, whose Normal highlight is usually
black on white unless you are using a colorscheme, the default is
usually "light").
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
> Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
>
> This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
>
> Thanks,
> Jeenu
I don't know why it happens but I know how to find out: next time the
problem happens, and after making sure Vim is in Normal mode (this
will usually mean hitting <Esc>, which will clear the Visual
highlighting) type
:verbose hi Visual
followed by <Enter>. Vim will answer by telling you not only exactly
what the Visual highlight is now set to, but also, which line of which
script (if any) last changed it. The script name and line can only be
missing if that highlight is either at its default, or was last set
manually.
Another possibly relevant setting is the 'background' setting, which
may be "dark" or "light" (without the quotes) and defines whether Vim
thinks that your current default background is a dark one or a bright
one respectively.
:verbose set bg
will tell you the current value and which script (if any) last set it.
Here it is more likely that no script will be mentioned, meaning the
value is still the default value (which, in Console Vim, can be either
"light" or "dark" depending on what Vim believes that you were using
immediately before startup; in gvim, whose Normal highlight is usually
black on white unless you are using a colorscheme, the default is
usually "light").
Best regards,
Tony.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Vim selection underlined rather than reversed
This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
Thanks,
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sunday, April 14, 2019
Vim visual selection underlined
Hi,
Normally, Vim visual selection is displayed terminal reverse color.
Sometimes I find that, after attaching to a perviously-detached
terminal session (tmux, screen, etc.), the visual selection is
displayed as bold underlines. See this question for example:
https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
The only solution I've found is to quit Vim, which I want to avoid.
Any ideas for troubleshooting this issue?
Thanks.
--
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Normally, Vim visual selection is displayed terminal reverse color.
Sometimes I find that, after attaching to a perviously-detached
terminal session (tmux, screen, etc.), the visual selection is
displayed as bold underlines. See this question for example:
https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
The only solution I've found is to quit Vim, which I want to avoid.
Any ideas for troubleshooting this issue?
Thanks.
--
Jeenu
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Friday, April 12, 2019
Re: Dead keys doesn't work in a terminal window in gvim
On Wed, Apr 10, 2019 at 02:51:45PM -0700, andalou wrote:
> I'm using gvim 8.1.1140 on Windows 7 with US-International layout
> keyboard.
>
> Normally, when I use the command prompt cmd.exe, with code page 1252,
> and press the ' key (dead key) and the "a" key I get "á", but on a
> terminal window in gvim I get 'a.
> The same happens with the keys "^" and "a". I should get "â", but I get
> ^a.
it depends on how the command prompt and terminal is activated. some
terminals don't display special characters, even when you set the
character set to it. probably neovim does it differently from cmd.exe
and gvim.
//meine
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I'm using gvim 8.1.1140 on Windows 7 with US-International layout
> keyboard.
>
> Normally, when I use the command prompt cmd.exe, with code page 1252,
> and press the ' key (dead key) and the "a" key I get "á", but on a
> terminal window in gvim I get 'a.
> The same happens with the keys "^" and "a". I should get "â", but I get
> ^a.
it depends on how the command prompt and terminal is activated. some
terminals don't display special characters, even when you set the
character set to it. probably neovim does it differently from cmd.exe
and gvim.
//meine
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thursday, April 11, 2019
Re: What is the quickest way to replace whole WORD with spaces?
0WvEr<space>
> On 10 Apr 2019, at 20:42, Igor Forca <igor2x@gmail.com> wrote:
>
> Hi,
>
> Sample data:
> aaa bbb:123:ccc ddd
>
> Desired result:
> aaa ddd
>
> What is the quickest way to replace second WORD with spaces?
>
> Now I use several keystrokes:
> fb - find letter b
> vaW - visual also WORD
> r<Space> - replace with space
>
> I know I can set a mapping like pressing minus key and do the task:
> noremap - vaWr<Space>
>
> but I am doing a lot of SSH, so don't want to mess with mappings on each of server.
>
> What is the quickest way to replace WORD with spaces in vanilla Vim settings?
>
> Thanks
>
> --
> --
> You received this message from the "vim_use" 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 Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> On 10 Apr 2019, at 20:42, Igor Forca <igor2x@gmail.com> wrote:
>
> Hi,
>
> Sample data:
> aaa bbb:123:ccc ddd
>
> Desired result:
> aaa ddd
>
> What is the quickest way to replace second WORD with spaces?
>
> Now I use several keystrokes:
> fb - find letter b
> vaW - visual also WORD
> r<Space> - replace with space
>
> I know I can set a mapping like pressing minus key and do the task:
> noremap - vaWr<Space>
>
> but I am doing a lot of SSH, so don't want to mess with mappings on each of server.
>
> What is the quickest way to replace WORD with spaces in vanilla Vim settings?
>
> Thanks
>
> --
> --
> You received this message from the "vim_use" 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 Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: In [g]vimdiff, is it possible to show the current different line in quickfix window?
Just realized that some one asked same Q about 8 years ago: https://stackoverflow.com/questions/565690/vimdiff-current-line-compare ~~~~~
Thanks,
Thanks,
On Wed, Apr 10, 2019 at 5:13 PM Kevin Gao <kkegao@gmail.com> wrote:
Hello friend,In [g]vimdiff, is it possible to show the current different line in quickfix window? (or some window in the bottom).This is what it looks like currently:My exception:It's very useful to find out the difference quickly when the line is long. Some handy diff tool such as Beyond Compare has this feature.I am not a vimscript expert. Not sure if some one has done this before???
Thanks,
Kevin
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wednesday, April 10, 2019
In [g]vimdiff, is it possible to show the current different line in quickfix window?
Hello friend,
In [g]vimdiff, is it possible to show the current different line in quickfix window? (or some window in the bottom).
This is what it looks like currently:
My exception:
It's very useful to find out the difference quickly when the line is long. Some handy diff tool such as Beyond Compare has this feature.
I am not a vimscript expert. Not sure if some one has done this before???
Thanks,
Kevin
Thanks,
Kevin
--
You received this message from the "vim_use" 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 Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Posts (Atom)