Tony Mechelynck wrote:

[..]

> The only solution that I know of consists of resizing the split-window 
> in question until it is no bigger than the whole file. Then there won't 
> be any "empty lines" in it, unless you scroll past the end of the file.

Hmm.. means I would need to resize the "window" to just one line when I 
start off with an empty buffer?

> To rapidly scroll a file which _is_ larger than its window so that the 
> bottom line of the file appears as the bottom line of the window, you 
> can for instance use
> 
>       ggG
> 
> i.e., go to top, then go back to the bottom.
> 
> 
> IMHO, the _best_ solution simply consists of accustoming yourself to the 
> notion that "tilde" lines mean space for growth past the present 
> end-of-file. 

IOW, surrender? Let's say I have developed a phobia to these tildes over 
the years and it is getting worse. :-)

I can think of a few other "solutions":

1. Patch the code obviously - cumbersome and a bit disappointing since 
one of vim's strong points is flexibility. Also, not very flexible since 
I would not be able to ever visualize the tildes without recompiling. 
Besides, I wouldn't know where in the code to start looking.

2. Switch color schemes when I need to make NonText visible. Not pretty 
but easy to implement - I guess I could even map a key combo to toggle 
the two color schemes with the code doing a "if g:colors_name="visible", 
colorscheme "invisible", else colorscheme "visible". Also loading a 
color scheme tends to be a little slow.

3. Changing the highlight specification for NonText on the fly: I don't 
use the "list" display mode all that often, mostly when I'm looking for 
trailing blanks. So I was thinking that I could set NonText to Black on 
Black in my color scheme and maybe define something that I could use in 
lieu of ":set list" that would (1) switch NonText to something visible, 
and (2) invoke ":set list". Sounds reasonable on the face of it but not 
sure how to implement that.

> (For "at-sign" lines in a partial wrapped line there _is_ a 
> better solution, but that's not what you're asking about.)

What are "at-sign" lines? I read something about that lately in the 
manual but I cannot seem to remember where.

Thanks,

Gen-Paul.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to