Sunday, December 29, 2019

Re: unchangeable lines

This probably isn't what the original poster had in mind, but this made me think what if vim could use a template file that acted as a mask?

Anywhere characters (X for example) existed in the mask file, those positions would not be changeable in the 'edit' file.

If the movement commands skipped over the masked positions, you'd have a really handy tool for editing forms.

I don't know to who this would appeal, can't imagine there are a lot of people jonesing over a modal editor for forms instead of an html form and mouse.



On Sunday, December 29, 2019 at 10:59:14 AM UTC-5, Salman Halim wrote:
Might be useful. I currently use something such as the InlineEdit plugin to extract the lines I want to modify. (This also helps in big files where syntax highlighting is slow.)

How would this be persisted? If it adds markers within the same file, the file won't be compatible with other editors. Maybe a second file would be saved alongside the main file, but with a different extension to indicate that it contains metadata. (Abc.txt and ABC.txt.vimmetadata)

For a Vim-script solution, you'd probably have to remap every single command that can change text (i, a, c, d, r, their upper-case variants, etc.) that would have to check to see whether the range of lines affected contains any of the fixed lines and abort if so. 

--

Salman

On Sun, Dec 29, 2019, 10:44 Efraim Yawitz <efraim...@gmail.com> wrote:
I wonder if this could be easily hacked into the code of vim by creating a new syntax group called Unchangeable or something and adding code to make it uneditable.

Maybe for now, create a syntax group and highlight it in a way that it reminds you not to change that text.

On Fri, 27 Dec 2019 at 09:58, Christian Brabandt <cbl...@256bit.org> wrote:

On Fr, 27 Dez 2019, Vladimir Stenbock wrote:

> Is it possible to mark some lines as unchangeable ?

This is not possible. A custom handmade plugin might work around this by
saving/restoring of lines, but in the core, Vim does not support this.

Best,
Christian
--
Eine Erfolgsformel kann ich dir nicht geben; aber ich kann dir sagen,
was zum Mißerfolg führt: Der Versuch, jedem gerecht zu werden.
                -- Herbert Swope

--
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191227075846.GN9787%40256bit.org.

--
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAPKXbB6iCUF-Xy%3D_OvgZSCW3nn4UknDcTsxaBWjz%3D80eaY%2By1g%40mail.gmail.com.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/8d7f9c26-ac19-42c1-ba7c-231263c2abb2%40googlegroups.com.

Re: unchangeable lines

Might be useful. I currently use something such as the InlineEdit plugin to extract the lines I want to modify. (This also helps in big files where syntax highlighting is slow.)

How would this be persisted? If it adds markers within the same file, the file won't be compatible with other editors. Maybe a second file would be saved alongside the main file, but with a different extension to indicate that it contains metadata. (Abc.txt and ABC.txt.vimmetadata)

For a Vim-script solution, you'd probably have to remap every single command that can change text (i, a, c, d, r, their upper-case variants, etc.) that would have to check to see whether the range of lines affected contains any of the fixed lines and abort if so. 

--

Salman

On Sun, Dec 29, 2019, 10:44 Efraim Yawitz <efraim.yawitz@gmail.com> wrote:
I wonder if this could be easily hacked into the code of vim by creating a new syntax group called Unchangeable or something and adding code to make it uneditable.

Maybe for now, create a syntax group and highlight it in a way that it reminds you not to change that text.

On Fri, 27 Dec 2019 at 09:58, Christian Brabandt <cblists@256bit.org> wrote:

On Fr, 27 Dez 2019, Vladimir Stenbock wrote:

> Is it possible to mark some lines as unchangeable ?

This is not possible. A custom handmade plugin might work around this by
saving/restoring of lines, but in the core, Vim does not support this.

Best,
Christian
--
Eine Erfolgsformel kann ich dir nicht geben; aber ich kann dir sagen,
was zum Mißerfolg führt: Der Versuch, jedem gerecht zu werden.
                -- Herbert Swope

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191227075846.GN9787%40256bit.org.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAPKXbB6iCUF-Xy%3D_OvgZSCW3nn4UknDcTsxaBWjz%3D80eaY%2By1g%40mail.gmail.com.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEcm0hAYwayF_dfcUhsT6mHPZ4YeTOUH%2BicgWi2RUopqWw%40mail.gmail.com.

Re: unchangeable lines

I wonder if this could be easily hacked into the code of vim by creating a new syntax group called Unchangeable or something and adding code to make it uneditable.

Maybe for now, create a syntax group and highlight it in a way that it reminds you not to change that text.

On Fri, 27 Dec 2019 at 09:58, Christian Brabandt <cblists@256bit.org> wrote:

On Fr, 27 Dez 2019, Vladimir Stenbock wrote:

> Is it possible to mark some lines as unchangeable ?

This is not possible. A custom handmade plugin might work around this by
saving/restoring of lines, but in the core, Vim does not support this.

Best,
Christian
--
Eine Erfolgsformel kann ich dir nicht geben; aber ich kann dir sagen,
was zum Mißerfolg führt: Der Versuch, jedem gerecht zu werden.
                -- Herbert Swope

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191227075846.GN9787%40256bit.org.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAPKXbB6iCUF-Xy%3D_OvgZSCW3nn4UknDcTsxaBWjz%3D80eaY%2By1g%40mail.gmail.com.

Re: Why don't :diffget and :diffput allow completion after hitting or ?

> I just created a pull request
> with this new feature:

Cool! I think it's already "merged". Thank you Dominique for your pull
request!
I'll test it when I have a chance.

Happy holidays!


--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191229150939.Horde.hSTS_pWBGfvP8KT5DfWjmBE%40tommy.heliohost.org.

Re: Why don't :diffget and :diffput allow completion after hitting or ?

jairlopez@etca.com.ve wrote:

> Thanks Dominique for your answer :-)
>
> > Completion could indeed be improved for diffput & diffget.
>
> Did you mean something like creating custom commands, like :Diffget
> and :Diffput, that behave in that way?

No. I meant we could add completion to the Vim :diffget
and :diffput commands. I just created a pull request
with this new feature:

https://github.com/vim/vim/pull/5409

Can you try it and provide feedback?

With this proposed change, `:diffget` and `:diffput`
complete to file names which are diff mode and which
are different than the current buffer. No completion
when current buffer is not in diff mode. No completion
either in vim tiny/small where FEAT_DIFF is not enabled.

Regards
Dominique

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAON-T_jerSmsyqwfO3_J7ejrLGaWzhaEQ-svyTOXo%2BzeXPT93g%40mail.gmail.com.

Saturday, December 28, 2019

Re: automatic redraw for multi-line syntax highlighting patterns

> If there are multi-line patterns, the sync mechanism needs to take care
> of any syntax items where more state becomes invalid. The extreme
> version is to use "syn sync fromstart". See ":help syn-sync".

My syn-sync setup does include "syn sync fromstart". Am I missing
something else in the syn-sync setup?

Thanks,

Tom

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAD_dSXiY5R-OyrF8Q8FqXpSejgbrQjFOvvbEy_X7mkvPWzFqwg%40mail.gmail.com.

Re: automatic redraw for multi-line syntax highlighting patterns

> the docs state (:help syn-multi-line) that syntax highlighting with
> multi-line patterns "mostly works as expected". I am not sure if this
> "mostly" includes automatic highlighting change of a multi-line syntax
> group when it's modified. Especially as soon as the pattern's end is
> destroyed. For example, take the commands of a session file ~/tmp/s.vim:
>
> call append(0, ['( comment?', ')'])syntax sync fromstarthi link m
> Commentsyntax match m /(.*\n)/
>
> They give us two lines highlighted as a comment (:hi Comment):
>
> ( comment?)
>
> Now, let's change the ')' into an 'x' via "2gg0rx". The test in the two
> lines does not match the defined syntax group anymore. But the display does
> not reflect this change right away. Instead I get something that's
> displayed partly as a comment (line 1) and partly as normal text (line 2):
>
> ( comment?)
>
> Note the different color of the two parentheses. I have to press CTRL-L to
> see the comment highlighting disappear completely. Having set syntax
> syncing to start from the very start of the file I would expect this to
> happen automatically. Is this imperfection the reason why the help says
> "mostly works" instead of "always works"? Or am I missing something?
>
> This is Vim 8.1.2337 (Huge version with GTK2 GUI) on Debian GNU/Linux,
> started with:
> vim --clean -S ~/tmp/s.vim
>
> Thanks in advance for all your insights,

When the text changes Vim by default assumes only that line needs to be
updated for syntax highlighting. In other words: the cached syntax
state at the start of the line is assumed to be valid.

If there are multi-line patterns, the sync mechanism needs to take care
of any syntax items where more state becomes invalid. The extreme
version is to use "syn sync fromstart". See ":help syn-sync".

--
ARTHUR: Be quiet!
DENNIS: --but by a two-thirds majority in the case of more--
ARTHUR: Be quiet! I order you to be quiet!
WOMAN: Order, eh -- who does he think he is?
ARTHUR: I am your king!
The Quest for the Holy Grail (Monty Python)

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912282157.xBSLvhPG001161%40masaka.moolenaar.net.

Re: Visual artifacts when running in some terminal emulators

I use terminator on  ubuntu.  I've been compiling my self from source
for about a year, so I'm now using 8.2.52, compiled this morning.

I have not seen any issues or video artifacts at all when using vim from
within terminator.  I also use guake; also, no issues or video artifacts.

I don't know if this matters, but no matter what I've tried, I cannot
get the binary to have lua.  So my vim still shows "-lua"

--rob solomon


On 12/28/19 10:21 AM, Tony Mechelynck wrote:
> On Sat, Dec 28, 2019 at 4:00 PM Олег Андриянов <o.andriyanov@gmail.com> wrote:
>> Hi!
>>
>> Recently I have built fresh vim 8.2 to use it's embedded terminal feature, and I started to notice some weird artifacts when inserting text. It's like vim forgets to redraw the screen or something. For example, here is a screenshot right after I run "vim-8.2 -u NONE" and hit "i" to start inserting text:
>>
>> https://i.imgur.com/mHq18Ni.png
>>
>> Note that I didn't actually enter anything after hitting "i". Also note that welcome screen text is still present on the screen — it must disappear when you switch to the insert mode. When I hit Ctrl+L, the artifacts disappear, but they come back every time I start inserting.
>>
>> I observe the problem only when I run vim inside terminator. When I use xterm, everything works fine. It also works well when I run vim inside GNU screen. There is no such issue with vim version 8.0.197 running inside the same terminator.
>>
>> I really like new features of vim 8.2. How can I work around this glitches, besides always starting vim inside GNU screen?
> Hm. My guess is that your Terminator executable pretends to be an
> xterm but doesn't act 100% like one, and that you hit one of those
> corner cases when it doesn't.
>
> Vim works well, and doesn't show those spurious characters, in the
> following circumstances:
> - when run as gvim (i.e. as a GUI)
> - when run in a "true" xterm
> - when run in a pseudo xterm which really mimics the behaviour of a
> true xterm. My konsole terminal (version 18.12.3) is one. There are
> others.
>
> Myself, I don't use Terminator, but maybe someone else (who does) is
> reading this.
>
> 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/7cef3050-eb8c-ba42-d2bf-dc9fd21fbff6%40fastmail.com.

Re: Visual artifacts when running in some terminal emulators

On Sat, Dec 28, 2019 at 4:00 PM Олег Андриянов <o.andriyanov@gmail.com> wrote:
>
> Hi!
>
> Recently I have built fresh vim 8.2 to use it's embedded terminal feature, and I started to notice some weird artifacts when inserting text. It's like vim forgets to redraw the screen or something. For example, here is a screenshot right after I run "vim-8.2 -u NONE" and hit "i" to start inserting text:
>
> https://i.imgur.com/mHq18Ni.png
>
> Note that I didn't actually enter anything after hitting "i". Also note that welcome screen text is still present on the screen — it must disappear when you switch to the insert mode. When I hit Ctrl+L, the artifacts disappear, but they come back every time I start inserting.
>
> I observe the problem only when I run vim inside terminator. When I use xterm, everything works fine. It also works well when I run vim inside GNU screen. There is no such issue with vim version 8.0.197 running inside the same terminator.
>
> I really like new features of vim 8.2. How can I work around this glitches, besides always starting vim inside GNU screen?

Hm. My guess is that your Terminator executable pretends to be an
xterm but doesn't act 100% like one, and that you hit one of those
corner cases when it doesn't.

Vim works well, and doesn't show those spurious characters, in the
following circumstances:
- when run as gvim (i.e. as a GUI)
- when run in a "true" xterm
- when run in a pseudo xterm which really mimics the behaviour of a
true xterm. My konsole terminal (version 18.12.3) is one. There are
others.

Myself, I don't use Terminator, but maybe someone else (who does) is
reading this.

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXvak6CVnosVWOUw_8KQxW4GEq9vMGToqDPEHb79qSNyqw%40mail.gmail.com.

Re: Why don't :diffget and :diffput allow completion after hitting or ?

Thanks Dominique for your answer :-)

> Completion could indeed be improved for diffput & diffget.

Did you mean something like creating custom commands, like :Diffget
and :Diffput, that behave in that way?

> But ideally, it should not be like :buffer, as :diffput :diffget
> should only complete to buffer which are in diffmode and
> also not complete the buffer name from which the diffput
> or diffget originates.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191228143211.Horde.2elTt2_GbX3QN-CDMzVMY99%40tommy.heliohost.org.

Visual artifacts when running in some terminal emulators

Hi!

Recently I have built fresh vim 8.2 to use it's embedded terminal feature, and I started to notice some weird artifacts when inserting text. It's like vim forgets to redraw the screen or something. For example, here is a screenshot right after I run "vim-8.2 -u NONE" and hit "i" to start inserting text:

https://i.imgur.com/mHq18Ni.png

Note that I didn't actually enter anything after hitting "i". Also note that welcome screen text is still present on the screen — it must disappear when you switch to the insert mode. When I hit Ctrl+L, the artifacts disappear, but they come back every time I start inserting.

I observe the problem only when I run vim inside terminator. When I use xterm, everything works fine. It also works well when I run vim inside GNU screen. There is no such issue with vim version 8.0.197 running inside the same terminator.

I really like new features of vim 8.2. How can I work around this glitches, besides always starting vim inside GNU screen?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/712582ab-874e-4404-81a7-3e42cdd7142a%40googlegroups.com.

Re: Why don't :diffget and :diffput allow completion after hitting or ?

Thanks Dominique for your answer :-)

> Completion could indeed be improved for diffput & diffget.
Did you mean something like creating custom commands, like :Diffget
and :Diffput, that behave in that way?

> But ideally, it should not be like :buffer, as :diffput :diffget
> should only complete to buffer which are in diffmode and
> also not complete the buffer name from which the diffput
> or diffget originates.


--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191228133542.Horde.rWrrt1AJgY-O-e6hCk-Vj02%40tommy.heliohost.org.

Re: Why don't :diffget and :diffput allow completion after hitting or ?

jairlopez@etca.com.ve wrote:

> Hello Vim community,
>
> This is what the documentation in :help E787 says:
>
> > The [bufspec] argument above can be a buffer number, a pattern for a buffer
> > name or a part of a buffer name. Examples:
> >
> > :diffget Use the other buffer which is in diff mode
> > :diffget 3 Use buffer 3
> > :diffget v2 Use the buffer which matches "v2" and is in
> > diff mode (e.g., "file.c.v2")
>
>
> It would be nice if it can allow completion like the :buffer command currently
> does; specially when dealing with merge conflicts as described here:
> https://stackoverflow.com/questions/14904644/how-do-i-use-vimdiff-to-resolve-a-git-merge-conflict
>
> Maybe I'm missing something, so I wonder why <Tab> and <C-D> doesn't work in
> :diffget and :diffput.

Completion could indeed be improved for diffput & diffget.
But ideally, it should not be like :buffer, as :diffput :diffget
should only complete to buffer which are in diffmode and
also not complete the buffer name from which the diffput
or diffget originates.

Regards
Dominique

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAON-T_jxXWoT%2BhS8wiYa6-rc8wSecHT2895gxcaqLzS4g-ffdA%40mail.gmail.com.

Why don't :diffget and :diffput allow completion after hitting or ?

Hello Vim community,

This is what the documentation in :help E787 says:

> The [bufspec] argument above can be a buffer number, a pattern for a buffer
> name or a part of a buffer name. Examples:
>
> :diffget Use the other buffer which is in diff mode
> :diffget 3 Use buffer 3
> :diffget v2 Use the buffer which matches "v2" and is in
> diff mode (e.g., "file.c.v2")


It would be nice if it can allow completion like the :buffer command currently
does; specially when dealing with merge conflicts as described here:
https://stackoverflow.com/questions/14904644/how-do-i-use-vimdiff-to-resolve-a-git-merge-conflict

Maybe I'm missing something, so I wonder why <Tab> and <C-D> doesn't work in
:diffget and :diffput.

Thanks in advanced.


--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191228123913.Horde.U363qe930xTtyjI2DnhOyek%40tommy.heliohost.org.

Visual artifacts when running in some terminal emulators

Hi!

Recently I have built fresh vim 8.2 to use it's embedded terminal feature, and I started to notice some weird artifacts when inserting text. It's like vim forgets to redraw the screen or something. For example, here is a screenshot right after I run "vim-8.2 -u NONE" and hit "i" to start inserting text:


Note that I didn't actually enter anything after hitting "i". Also note that welcome screen text is still present on the screen — it must disappear when you switch to the insert mode. When I hit Ctrl+L, the artifacts disappear, but they come back every time I start inserting.

I observe the problem only when I run vim inside terminator. When I use xterm, everything works fine. It also works well when I run vim inside GNU screen. There is no such issue with vim version 8.0.197 running inside the same terminator.

I really like new features of vim 8.2. How can I work around this glitches, besides always starting vim inside GNU screen?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJeKBY_M8FEkHMrtGf6-EdgGdPDGh0vEd5j-ot7LbfjwHzB%2BwQ%40mail.gmail.com.

Compile vim while pyenv + anaconda installed in the os, failed with: checking Tcl version... pyenv: tclsh8.5: command not found

Hi,

I use pyenv to manage python versions, and I've installed some
python's versions as follows:

$ pyenv versions
system
2.7.17
3.5.9
* 3.6.9 (set by /home/werner/.pyenv/version)
3.7.5
3.8.0
anaconda3-2019.10
anaconda3-4.3.0
anaconda3-5.3.0
anaconda3-5.3.1

In this case, I try to compile vim from the git version, but failed at
the configure stage:

$ ./configure --enable-fail-if-missing --enable-autoservername
--enable-cscope --enable-fontset --enable-multibyte
--enable-luainterp --enable-perlinterp
--enable-pythoninterp=yes --enable-python3interp=yes
--enable-rubyinterp --enable-tclinterp --enable-gui=gtk3
--enable-terminal --enable-xim --with-x --with-luajit
--with-lua-prefix=/usr/local --with-features=huge
[...]
checking for tclsh8.5... /home/werner/.pyenv/shims/tclsh8.5
checking Tcl version... pyenv: tclsh8.5: command not found

The `tclsh8.5' command exists in these Python versions:
anaconda3-4.3.0

too old; need Tcl version 8.0 or later
configure: error: could not configure Tcl


Any hints for solving this issue?
--
Hongsheng Zhao <hongyi.zhao@gmail.com>
Institute of Semiconductors, Chinese Academy of Sciences
GnuPG DSA: 0xD108493

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAGP6PO%2BnLg-2%2B2Bt8sOhBQJZr3tSVQEo547w_UFbbt3SjOHorA%40mail.gmail.com.

Visual artifacts when running in some terminal emulators

Hi!

Recently I have built fresh vim 8.2 to use it's embedded terminal feature, and I started to notice some weird artifacts when inserting text. It's like vim forgets to redraw the screen or something. For example, here is a screenshot right after I run "vim-8.2 -u NONE" and hit "i" to start inserting text:


Note that I didn't actually enter anything after hitting "i". Also note that welcome screen text is still present on the screen — it must disappear when you switch to the insert mode. When I hit Ctrl+L, the artifacts disappear, but they come back every time I start inserting.

I observe the problem only when I run vim inside terminator. When I use xterm, everything works fine. It also works well when I run vim inside GNU screen. There is no such issue with vim version 8.0.197 running inside the same terminator.

I really like new features of vim 8.2. How can I work around this glitches, besides always starting vim inside GNU screen?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJeKBY9SJgbCSCk%3DijFQTWEVSSKmREEnWuts6Gk-wChSXzp27Q%40mail.gmail.com.

Friday, December 27, 2019

Re: automatic redraw for multi-line syntax highlighting patterns


On Sat, Dec 28, 2019 at 12:32 AM Tom M <7tommm@gmail.com> wrote:
Hi,

the docs state (:help syn-multi-line) that syntax highlighting with multi-line patterns "mostly works as expected".  I am not sure if this "mostly" includes automatic highlighting change of a multi-line syntax group when it's modified. Especially as soon as the pattern's end is destroyed. For example, take the commands of a session file ~/tmp/s.vim:
call append(0, ['( comment?', ')'])  syntax sync fromstart  hi link m Comment  syntax match m /(.*\n)/  
They give us two lines highlighted as a comment (:hi Comment):
( comment?  )
Now, let's change the ')' into an 'x' via "2gg0rx". The test in the two lines does not match the defined syntax group anymore. But the display does not reflect this change right away. Instead I get something that's displayed partly as a comment (line 1) and partly as normal text (line 2):
( comment?  )
 Typo here. This last screen looks, of course, like this:
( comment?  x
Sorry for the confusion.

Tom

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAD_dSXjKeSDVXJ3XfHuLWHusKL0c5%3DmSLhDoe7LKbFs4DOaJ1g%40mail.gmail.com.

automatic redraw for multi-line syntax highlighting patterns

Hi,

the docs state (:help syn-multi-line) that syntax highlighting with multi-line patterns "mostly works as expected".  I am not sure if this "mostly" includes automatic highlighting change of a multi-line syntax group when it's modified. Especially as soon as the pattern's end is destroyed. For example, take the commands of a session file ~/tmp/s.vim:
call append(0, ['( comment?', ')'])  syntax sync fromstart  hi link m Comment  syntax match m /(.*\n)/  
They give us two lines highlighted as a comment (:hi Comment):
( comment?  )
Now, let's change the ')' into an 'x' via "2gg0rx". The test in the two lines does not match the defined syntax group anymore. But the display does not reflect this change right away. Instead I get something that's displayed partly as a comment (line 1) and partly as normal text (line 2):
( comment?  )
Note the different color of the two parentheses. I have to press CTRL-L to see the comment highlighting disappear completely.  Having set syntax syncing to start from the very start of the file I would expect this to happen automatically. Is this imperfection the reason why the help says "mostly works" instead of "always works"? Or am I missing something?

This is Vim 8.1.2337 (Huge version with GTK2 GUI) on Debian GNU/Linux, started with:
vim --clean -S ~/tmp/s.vim

Thanks in advance for all your insights,

Tom

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAD_dSXiPJzHXRqpWgtKQPS0Y8UhBkk3Ns6iCtJW566jKgcJysw%40mail.gmail.com.

Thursday, December 26, 2019

Re: unchangeable lines

On Fr, 27 Dez 2019, Vladimir Stenbock wrote:

> Is it possible to mark some lines as unchangeable ?

This is not possible. A custom handmade plugin might work around this by
saving/restoring of lines, but in the core, Vim does not support this.

Best,
Christian
--
Eine Erfolgsformel kann ich dir nicht geben; aber ich kann dir sagen,
was zum Mißerfolg führt: Der Versuch, jedem gerecht zu werden.
-- Herbert Swope

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20191227075846.GN9787%40256bit.org.

unchangeable lines

Is it possible to mark some lines as unchangeable ?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANXeduMrp7iYOQK0O8YxgTnkOUSTKraepLtEahMbr3GZeUbkJA%40mail.gmail.com.

Tuesday, December 24, 2019

Re: Tabs in GVim 8.2

Hello,

Quick update: I just updated to 8.2.0037 and the problem has gone away. I looked through the list of patches, but couldn't figure out what was changed. However, I'm pleased it's gone.

Thanks to everybody who looked into it for me!

Best regards,

Salman

On Tue, Dec 24, 2019 at 5:25 AM Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
On Tue, Dec 24, 2019 at 10:48 AM Tekki <tekki@tekki.ch> wrote:
>
> If I open a single file the name of the file is in the header of the window and there is no empty line at the top. If I open a second tab the tabbar appears.
> GVIM 8.2.12 on Windows 10 Pro 19041.1.

To display the tab bar even if there is only one tab, :set showtabline=2
>
> Am Montag, 23. Dezember 2019 00:35:47 UTC+1 schrieb Salman Halim:
>>
>> Did anybody else notice this in Windows?

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXuobowih87hvj1xG-4do8hRW0qoqUEq-kyBfwxmuo0xfw%40mail.gmail.com.


--
 
Salman

I, too, shall something make and glory in the making.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEcK35PaO8Bj4nVmXLwS50dZBv%3DwYxVQFz9njo_%3DtD5npQ%40mail.gmail.com.

Re: How to profile next command

On Tue, Dec 24, 2019 at 11:37 AM Ni Va <nivaemail@gmail.com> wrote:
>
> if it can help.
>
> This mapping is bad : nnoremap noh :noh<cr>
>
> It takes 2 seconds before jumping to next occurence when you search for a sentence.

This is expected: when you type n to search for next match after
having defined this mapping, Vim waits for 'timeoutlen' millseconds
(default 1000) to see if an o is coming (and if it is, then an h). You
could either define a second mapping, e.g. ":nnoremap nn n" or forgo
your noh mapping altogether.

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXv%3D6GN%3D%3DaYtU5DUqhi4jRo0sR0Ow4F0qmopPy74JxidDw%40mail.gmail.com.

Re: How to profile next command

if it can help.

This mapping is bad :  nnoremap noh :noh<cr>

It takes 2 seconds before jumping to next occurence when you search for a sentence.


Le mardi 24 décembre 2019 11:16:24 UTC+1, Ni Va a écrit :
Hi,

I note that next command has a slow jumping to next odd.

How can I profile next command  ?

Thank you
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/78fad1a1-b7bd-40a7-bd13-9f20809bcb7f%40googlegroups.com.

Re: Tabs in GVim 8.2

On Tue, Dec 24, 2019 at 10:48 AM Tekki <tekki@tekki.ch> wrote:
>
> If I open a single file the name of the file is in the header of the window and there is no empty line at the top. If I open a second tab the tabbar appears.
> GVIM 8.2.12 on Windows 10 Pro 19041.1.

To display the tab bar even if there is only one tab, :set showtabline=2
>
> Am Montag, 23. Dezember 2019 00:35:47 UTC+1 schrieb Salman Halim:
>>
>> Did anybody else notice this in Windows?

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXuobowih87hvj1xG-4do8hRW0qoqUEq-kyBfwxmuo0xfw%40mail.gmail.com.

How to profile next command

Hi,

I note that next command has a slow jumping to next odd.

How can I profile next command  ?

Thank you
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/94ca93e8-af0f-4fc6-9953-688eb3164028%40googlegroups.com.

Re: Tabs in GVim 8.2

If I open a single file the name of the file is in the header of the window and there is no empty line at the top. If I open a second tab the tabbar appears.
GVIM 8.2.12 on Windows 10 Pro 19041.1.

Am Montag, 23. Dezember 2019 00:35:47 UTC+1 schrieb Salman Halim:
Did anybody else notice this in Windows?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/0d21abab-81f8-4b24-b097-f4eab733124b%40googlegroups.com.

Monday, December 23, 2019

Vim calendar for 2020 available

Happy New Year to all Vim users!

2019 was a good Vim year with a few new features, many bug fixes and
improved test coverage. This is included in the recent 8.2 release,
which went out smoothly.

For the coming year the main goal is to improve the execution speed of
Vim script. I have started experimenting with some ideas, and it looks
hopeful. An increase of 10 to 100 times can be expected. More about
that soon.

I have updated the handy desktop calendar for 2020. It prints on one
sheet of paper and, after folding and applying a bit of glue, stands on
your desk.

It is available in English and Dutch. You can find the PDF files on my
website: https://moolenaar.net/#Calendar

Happy Vimming!

--
FATHER: Did you kill all those guards?
LAUNCELOT: Yes ... I'm very sorry ...
FATHER: They cost fifty pounds each!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912231705.xBNH55sD015131%40masaka.moolenaar.net.

[i and [I don't show first occurrence in python files

If I've a Python file

from foo import bar

....

   qux = bar(...)

And I place the cursor on the 'bar' function invocation, and do [i or [I, I get E387 - Match is on the current line. From my experience with other text/source files (Java, for example) and documentation, I fully expect it to list the first occurrence, which is the very first import line.

I checked that [i and [I are not mapped to anything else.

Additionally, if I reset ft (while still inside the python file), it works

Can someone hint at why this is happening?

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b72b0c48-f889-4a64-be67-de8f79175055%40googlegroups.com.

Wrap with indent

Hi, this is for normal text editing rather than programming. I would like the first line of a paragraph to begin in column 1, and all auto-wrapped lines in that para after line 1 to have an indent of eight spaces:


This is a sample (and narrow) paragraph to
        illustrate the effect I am trying to
        achieve
.

What settings should I be looking at to achieve this?

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d870e39c-b0b3-4d3a-85ad-3517a0ce2966%40googlegroups.com.

Re: Tabs in GVim 8.2

Yes, except that this is how it looks when I start up:



Note the blank line below the toolbar; on 8.1, this is how it looks:



I can get it to work by manually executing :set guioptions-=e guioptions+=e (not in the vimrc; has to be done after startup), but I don't know of another way to fix it. Simply adding new tabs doesn't do it.

Nothing changed in my configuration other than the switch to 8.2.

Thank you,

Salman

On Mon, Dec 23, 2019 at 8:32 AM Ni Va <nivaemail@gmail.com> wrote:
Hi Salman,

Do you talk about the tab feature like in this screenshot ?
On Windows 10, compiled today in 32bit version 8.2 patch 33

Le lundi 23 décembre 2019 00:35:47 UTC+1, Salman Halim a écrit :
Did anybody else notice this in Windows?

--

Salman

On Fri, Dec 20, 2019, 19:57 Salman Halim <salma...@gmail.com> wrote:


On Fri, Dec 20, 2019, 17:47 Tony Mechelynck <antoine....@gmail.com> wrote:
P.S. Tested in 8.2.24 (Big) with GTK2 GUI on openSUSE Linux Leap 15.1
with GTK2 2.4.32 and XOrg 1.20.3

Might be a Windows only thing. I really appreciate your testing it. Thank you.

Salman

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d7c223d0-dc82-4d6d-a05c-432880ea0507%40googlegroups.com.


--
 
Salman

I, too, shall something make and glory in the making.

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEeLvPbT47sD_siKutyU7iXi5scOQx4Q4Zu-W7tE5q-PuA%40mail.gmail.com.

Re: Tabs in GVim 8.2

Hi Salman,

Do you talk about the tab feature like in this screenshot ?
On Windows 10, compiled today in 32bit version 8.2 patch 33

Le lundi 23 décembre 2019 00:35:47 UTC+1, Salman Halim a écrit :
Did anybody else notice this in Windows?

--

Salman

On Fri, Dec 20, 2019, 19:57 Salman Halim <salma...@gmail.com> wrote:


On Fri, Dec 20, 2019, 17:47 Tony Mechelynck <antoine....@gmail.com> wrote:
P.S. Tested in 8.2.24 (Big) with GTK2 GUI on openSUSE Linux Leap 15.1
with GTK2 2.4.32 and XOrg 1.20.3

Might be a Windows only thing. I really appreciate your testing it. Thank you.

Salman

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d7c223d0-dc82-4d6d-a05c-432880ea0507%40googlegroups.com.

Profiling slow buffer search

Hi,

In buffer that contains several "foobar" string, I note that pressing 'n' (next) spends more than one second.
I think one of installed plugins is at the origin of this problem.


I have tested with no interesting results

profile start $tmp/profile.log
profile func * 
>>>> then typing '/vim' and typing 'n'
exit


How can I profile with more accuracy ?
Thank you
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/712fc955-bf06-4b8e-90c7-33ce16e9fa60%40googlegroups.com.

Sunday, December 22, 2019

Re: Tabs in GVim 8.2

Did anybody else notice this in Windows?

--

Salman

On Fri, Dec 20, 2019, 19:57 Salman Halim <salmanhalim@gmail.com> wrote:


On Fri, Dec 20, 2019, 17:47 Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
P.S. Tested in 8.2.24 (Big) with GTK2 GUI on openSUSE Linux Leap 15.1
with GTK2 2.4.32 and XOrg 1.20.3

Might be a Windows only thing. I really appreciate your testing it. Thank you.

Salman

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEeThDqeQzEKhgLeVTLtQmG9xDjUkci9ErTi7Wy%3DGUEmSQ%40mail.gmail.com.

Re: Export Vim screen with multiple vertical splits to HTML ?



On Saturday, December 21, 2019 at 4:21:46 AM UTC-6, Philip Rhoades wrote:
People,

I know about exporting Vim diffs to HTML but I have a situation where it
is convenient for me to look at a bunch of files in Vim each in a
vertical split.  Now while it is convenient for me to look at these
files this way, I cannot easily share this convenient view with other
(non-tech) people.  What I am thinking is that it would be nice to
export this view to HTML in the same way a diff view can be exported.  
The end result I guess would be multiple, side-by-side HTML divs that
are independently vertically scrollable.

Can anyone comment if this is doable? - perhaps as a Vim plugin?



This sounds easy enough to implement and probably useful in some situations.

It's not a current feature however.

There might be a wrapper for this, all you'd really need to do is create two divs with scrolling enabled via CSS, put them in a table with the desired layout (or use CSS), and copy the body of the generated HTML for each window into each area. Then copy the styles into the header. There might be some more adjustment needed for line number IDs, etc. depending on your options.

You can make a feature request here if you want (for now, I'll migrate issues when I find a new home for the repository): https://bitbucket.org/fritzophrenic/vim-tohtml

I have not had much time for development on the plugin recently but this is certainly a feature I'd consider adding. Not sure of the best UI for it though.

There was a similar plugin to TOhtml but it looks like that also has been inactive recently. I thought maybe they had a feature like this but I don't see it right away in the description: https://www.vim.org/scripts/script.php?script_id=3113

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/7dd276b7-4cdc-44ed-a146-5bfbc30759b6%40googlegroups.com.

Saturday, December 21, 2019

Export Vim screen with multiple vertical splits to HTML ?

People,

I know about exporting Vim diffs to HTML but I have a situation where it
is convenient for me to look at a bunch of files in Vim each in a
vertical split. Now while it is convenient for me to look at these
files this way, I cannot easily share this convenient view with other
(non-tech) people. What I am thinking is that it would be nice to
export this view to HTML in the same way a diff view can be exported.
The end result I guess would be multiple, side-by-side HTML divs that
are independently vertically scrollable.

Can anyone comment if this is doable? - perhaps as a Vim plugin?

Thanks,

Phil.
--
Philip Rhoades

PO Box 896
Cowra NSW 2794
Australia
E-mail: phil@pricom.com.au

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/85390a23eac74ab3582013d8cf6ca038%40pricom.com.au.

Friday, December 20, 2019

Re: Tabs in GVim 8.2



On Fri, Dec 20, 2019, 17:47 Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
P.S. Tested in 8.2.24 (Big) with GTK2 GUI on openSUSE Linux Leap 15.1
with GTK2 2.4.32 and XOrg 1.20.3

Might be a Windows only thing. I really appreciate your testing it. Thank you.

Salman

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEeS0r3ttpDSN7QXPf52HCAKUyJz%2BCbMBFOkme5W5fWcJg%40mail.gmail.com.

Re: Tabs in GVim 8.2

P.S. Tested in 8.2.24 (Big) with GTK2 GUI on openSUSE Linux Leap 15.1
with GTK2 2.4.32 and XOrg 1.20.3

--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXt0uKL75w2Z%3DicXADZdZC95y_h0tc-J6W9j1HF%2BU5Q_Qw%40mail.gmail.com.

Re: Tabs in GVim 8.2

On Fri, Dec 20, 2019 at 10:39 PM Salman Halim <salmanhalim@gmail.com> wrote:
> On Fri, Dec 20, 2019, 16:26 Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
>> On Fri, Dec 20, 2019 at 9:15 PM Salman Halim <salmanhalim@gmail.com> wrote:
>> >
>> > Hello,
>> >
>> > I switched to GVim 8.2 (Windows 10) and no longer see the tab list at the top. I tried both my self-compiled version and the version with patch 24 off GitHub. I also tried two different computers, both with Windows 10.
>> >
>> > I've gone back to 8.1 because I rely upon multiple tabs in my daily workflow, but figured it would be worth finding out whether it was just something with my configuration.
>> >
>> > Thank you,
>>
>> I see tabs at the top even in gvim 8.2, but I'm using text-style tabs
>> in both vim and gvim, thanks to the following code in my vimrc (the
>> "if" wrapping avoids problems with versions earlier than Vim 7 but
>> also with limited featuresets of any version):
>>
>> ...
>>
>> Best regards,
>> Tony.
>
>
> Switching to non-gui tabs via removing e from &guioptions shows the non-gui tabs just fine. Interestingly, then adding e BACK shows the gui tabs. I just get an empty space otherwise.
>
> Would you mind trying the GUI tabs, please? You'd have to enable them in your vimrc because doing it after works for me, also, and wouldn't be representative of my experience. Should be as simple as not taking e out, I'm thinking.
>
> Thanks, Tony.

Adding back e in my vimrc on the line where it sets 'guioptions' (by
value rather than by increment) shows me GTK-style tabs in my gvim Big
build with GTK2 GUI. Since 'guitablabel' is (by default) empty, I see
Vim's default tab label on them. Then ":set go-=e" manually shows my
preferred text-style tabs, of narrower height, with the label defined
by the 'tabline' setting in my vimrc, as previously shown.

FWIW, this is the relevant section of my modified vimrc (where ¬ in
the comments means "not"); as a second test I completely commented
away the ":set guioptions=" line (resulting in the default aegimrLtT
value), and GTK-style tabs were still present.

" 'guioptions': GUI options
" !: run external commands (or the shell) in a terminal window
" ¬a: no autoselect for "+
" ¬P: ditto for "*
" ¬A: ditto for modeless selection
" c: use console dialogs (not popup dialogs) for simple choices
" ¬e: use text-style, tabs even in the GUI
" ¬f: use fork() to start the GUI
" i: use a GUI icon if possible
" m: menu bar is present
" ¬M: source $VIMRUNTIME/menu.vim
" g: inactive menuitems are shown (greyed-off)
" t: include tearoff menuitems
" T: include toolbar
" r: right-hand scrollbar is always present
" ¬R: not only when vertically split
" ¬l: left-hand scrollbar is not always present
" L: only when vertically split
" ¬b: no bottom scrollbar
" ¬h: bottom scrollbar is not limited to size of cursor line
" ¬v: do not force vertical button layout in dialogs
" p: do not include X11 pointer callbacks (required by some WMs)
" ¬F: don't add a Footer (Motif-only)
" set guioptions=!cgimrLtTp
set guioptions=!cegimrLtTp

Since I have no Windows system, I cannot compare this with what would
happen under Windows with the same vimrc.

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXvYMReYV1dEuB6nXt1yrxkSOWxJXhXraXheWjPQtPi%2BNg%40mail.gmail.com.