On Tue, Sep 02, 2014 at 08:55:48PM +0200, Christian Brabandt wrote:
> Hi Tim!
> On Di, 02 Sep 2014, Tim Chase wrote:
> > The documentation for 'sol' does mention "buffer changing commands" which
> > could ambiguously be interpreted to mean that it should take
> > effect when a file is opened for the first time (after all, it's
> > changing from no-loaded-buffer to a now-loaded-buffer). I'm not sure
> > I'd go so far as to call it a bug, but perhaps an unfortunate
> > inconsistency or documentation ambiguity.
> >
> > And I suspect that anybody who flies with 'nosol' set would be irked
> > by the behavior much as you mention.
I do and I am
> I am not sure I follow. What exactly would you call a bug here?
> I have set 'nosol' in my .vimrc for years and haven't noticed any wrong
> behaviour.
quote clipping has removed my description of the irksome behavior -- in
a nutshell, it is that when I open a text module with a first line that
has 46 blanks before the first non-blank character, the cursor is placed
on line one COLUMN 47. If I start out by scrolling with j, it can be a
real trick to see, especially when I am expecting it to be over on the
left
when using vim and nocursorline and nocursorcolumn for me the cursor is
a mere underscore, difficult to see, and it helps immeasurably if I know
where it is without having to look for it
for me there are two ways forward: 1) use an autocommand as Tim
suggested, or 2) learn to hit 0 before I start scrolling
I am proceeding with (1), as I want the cursor to be on line 1 column 1
whenever I open a new buffer -- so far the autocommand hasn't broken any
of my scripts
--
_|_ _ __|_|_ ._ o|
|_(_)(_)|_| ||_)||<
|
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
