Re: How to bind scrolling horizontal split windows?

On 2022-02-21, Igor wrote:
> Hi,
> I am using Vim 7.4 on Linux.

> Now to the actual problem. I have text of multiple columns with header. When I
> move down a buffer I no longer see head of columns, so I vertically slit
> window. Top window is at first line position to see column headers, bottom
> window I use to see data in e.g. 1000 row. I can easily in e.g. column 5 the
> data in line 1000 and header from line 1. But when in e.g. bottom window I
> scroll to the right, I would like both windows to scroll to the right like they
> are bound together, so I can see e.g. 100 columns body and header, but instead
> only current buffer in current window is scrolled.

The 'scrollopt' option lets you choose to bind vertical scrolling
(the default), horizontal scrolling, or both.

:e some_file
:set nowrap
:set scrollopt-=ver
:set scrollopt+=hor
:set scrollbind
:split

See

:help 'scrollopt'

> Now instead of ":sp" in second command turn on vertical split screen ":vsp" How
> to turn on vertical scrollbind?

I'm not sure I understand you. Vertical scrollbinding is the
default. Do you mean that you want something like this, where the
buffer is vertically split but each half has the column headers
above it, with the vertically-split windows vertically scrollbound
while the horizontally-split windows are horizontally scrollbound?

+---------+---------+
| headers | headers |
+---------+---------+
| | |
| body | body |
| | |
+---------+---------+

Unfortunately for this case, 'scrollopt' is a global option. You
can have all scrollbound windows scroll together horizontally or
vertically (or both), but you can't have some windows bound
horizontally while others are bound vertically.

Regards,
Gary

--
--
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/20220221140135.GA19760%40phoenix.

Sven Guckes passed away

Forwarding this text from Antonio Colombo:

==================

Our friend Sven Guckes died in Berlin on February 20, 2022.
He was diagnosed with a brain tumor in December 2021.
He went to a hospital, but surgeons could not do much for him.
At the end of January he was moved to a Hospice.
A group of friends has been with him as much as possible during all his
sickness.
He died while Pugs, one of his friends, was with him.
They had just finished a chat, and Sven was smiling, but then he quieted
down and in a few moments he did not breathe any more.

Sven (when he was still a student at the Free University of Berlin) was very
active in the Vim development team in the Nineties. He was the one who set
up the vim.org domain. Later on he had the idea of "What is Vim?", an
explanation of Vim in six kilobytes, and helped with some versions of
Vimtutor.

Sven worked (and gave talks) also on a lot of other free software projects,
let us remember here just "plain" vi and mutt, but there are several
others. He had friends all over the world, and helped them, for software
problems and for real life problems in any way he could.

Let us recall here just one of his "pet projects", the mythical
"alternate.fan.warlord" FAQ, in which appears one of his signatures,
in newsgroup alt.fan.warlord.

Vale, Sven!

==================


I met Sven only a couple of times. What I remember most is his never
ending enthusiasm. He was a good person.

I would like to dedicate the upcoming Vim 9.0 release to Sven in his
memory.

Article in German: https://linuxnews.de/2022/02/sven-guckes-verstorben/
Hacker news: https://news.ycombinator.com/item?id=30410077

--
hundred-and-one symptoms of being an internet addict:
91. It's Saturday afternoon in the middle of May and you
are on computer.

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ 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/20220221134844.047981C0FE0%40moolenaar.net.

How to bind scrolling horizontal split windows?

Hi,

I am using Vim 7.4 on Linux.

Open text file:

:e some_file

Split the same buffer to another window:

:sp

Turn off long line wrap:

:set nowrap

Bind scrolling of both windows:

:set scrollbind

Now move up and down a buffer and both windows scroll together.

Now to the actual problem. I have text of multiple columns with header. When I move down a buffer I no longer see head of columns, so I vertically slit window. Top window is at first line position to see column headers, bottom window I use to see data in e.g. 1000 row. I can easily in e.g. column 5 the data in line 1000 and header from line 1. But when in e.g. bottom window I scroll to the right, I would like both windows to scroll to the right like they are bound together, so I can see e.g. 100 columns body and header, but instead only current buffer in current window is scrolled.

Now instead of ":sp" in second command turn on vertical split screen ":vsp" How to turn on vertical scrollbind?

Regards

--
--
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/31223dbc-a87f-472b-9c5e-b037cbe6b374n%40googlegroups.com.

Proper use of histdel()

Hi everybody,

I'd like to delete the last 100 entries in command line history. I've tried

call histdel(":", -100) and various alternatives using histdel() but I don't get it to work.

So far the only way I've discovered is directly editing _viminfo,

but that's a bit cumbersome.

Any suggestions from experts welcome!

--
--
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/787eebbc-f590-4937-b595-4bd62ba8618cn%40googlegroups.com.

Re: Vim9 - Can not get compile to recognize a deep variable

------- Original Message -------

On Wednesday, February 16th, 2022 at 3:27 PM, Chainsaw <chainsawuser@cfl.rr.com> wrote:

> Bram,
>
> First, thank you for Vim. What you have created is amazing, and has literally filled every void I had in my workflow, from text editing, to writing software to streamline specific tasks, and infinitely more. The only thing I don't like is I use Vim so much, that I find myself typing a ':' everywhere, on desktop, in title bar of browser, and I tried to save a file today in Word by typing ':w'.

I do this, too. I'm so accustomed to using Vim's shortcuts that I had to install Pentadactyl and its forks on my web browsers. It's the worst addiction; it's the best addiction.

--
--
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/OmSSSlXLpAq3G76Jsfr94NQwMBAthF7Bslm8k-GUzxWBPWdUWVFKpDEcZL4uqs8KiBOK75eXMdYUVWLkBkKxbU62YwqvuZyl0iCcUdqrTzs%3D%40protonmail.com.

Re: Vim9 - Can not get compile to recognize a deep variable

> In most cases you can use a script-local variable. In Vim9 script you
> can give these a type and that will be enforced. This works best,
> because references to the variable will be in the same script, the
> knowledge of what the variable is for and what it's type is is
> localized.

Exactly how I approach every new function, global is my last resort.

Thanks for your replies.
Samson

--
--
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/20220217090024.00005985%40cfl.rr.com.

Re: Vim9 - Can not get compile to recognize a deep variable

> Like 'var udp: list<string>', it would be nice to declare the global
> equivalent 'g:udp: list<any>' (redundant, but reminds me what Vim is
> expecting when I look at the code).

The problem is that the type can't be enforced. In legacy script it has
always been possible to assign anything to a global variable. Also it
can be deleted with :unlet and given a completely different value.

In most cases you can use a script-local variable. In Vim9 script you
can give these a type and that will be enforced. This works best,
because references to the variable will be in the same script, the
knowledge of what the variable is for and what it's type is is
localized.

Theoretically it would be possible to add a new type of global variable
that works differently. I do not see enough need for this, while it
does add complexity. And especially that when using g:someVar you don't
know where it was defined and what kind of variable it is.

--
hundred-and-one symptoms of being an internet addict:
56. You leave the modem speaker on after connecting because you think it
sounds like the ocean wind...the perfect soundtrack for "surfing the net".

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ 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/20220217105912.852821C0FE0%40moolenaar.net.