Win32 vim.exe blows up reading from stdin

[Dave Roberts]

Hello all,

Somewhere between v7.0.118 and v7.0.131 Vim started blowing up when 
started with a "-" to read from stdin. Ex. "vim -u NONE -"


If no one else is having this problem I'll supply more 
compile/environment info.


I use gvim as a "less" program all the time so I know this wasn't 
happening earlier.


Thanks,

- Dave

Re: Convert2HTML Again

[Edd Barrett]

Hi Guys,

On 10/10/06, Benji Fisher <[EMAIL PROTECTED]> wrote:

On Tue, Oct 10, 2006 at 01:40:04PM +0100, Edd Barrett wrote:



 Be careful about what you ask (or wish) for:  you just might get
it! ;)


I tryed to make it sound as polite as i could, I'm not very good at
this. My aplogies :)



 The samples look fine to me (using Mozilla 1.7.12 on Linux).  I
would like to see an example where the background color changes, if only
so that I can see some situation where

 (text) 

looks simpler (by rudimentary measures such as character count) than

 (text) 


I'm not sure what you mean here. Please explain...



 How does the encoding get set?  For example, in xhtml.html I see



If I have
:set enc=utf-8
will I get utf-8 in that line?


I have a feeling that this is hardcoded. Ill add it to my list.



 Have you actually tested for W3C compliance?


Yes. All 8 tests fully pass.


 Very minor points:  you might want to change the line

if exists("html_font")

to

if exists("g:html_font")


Will do



Some readers will find this clearer, and if those lines ever get wrapped
in a function, then it will actually make a difference.  Please fix the
indentation in places like this:

-  if exists("use_xhtml")
-let s:LeadingSpace = ' '
-  else
 let s:LeadingSpace = ' '
-  endif


I thought I had. Ill have a look.



HTH --Benji Fisher




Thanks for your time Benji!

Best Regards

Edd

Re: long echomsg + 'set shortmess+=T' + norm-vs-without-norm

[A.J.Mechelynck]

Yakov Lerner wrote:

I observe strange behaviour related to 'set shortmess+=T' . Sometimes
this 'T' flag shortens long messages, sometimes it does not.
To see:
1.
vim -u NONE
2.
:set nocp shortmess=aT
:nmap ZB :echomsg repeat('a',&co+10)
3.
Press ZB. You get long message and 'Press Enter' prompt.
4.
Type
:norm ZB
You get shortened message, and no ''Press Enter' prompt.


...but only if you had first cleared the Hit-Enter prompt. If you enter it at 
the Hit-Enter prompt (instead of hitting Enter or Space) you get long message 
again, with a fresh Hit-Enter prompt.



5.
Type
:echomsg repeat('a',&co+10)
This behaves like (3), not like (4).

I don't understand why (3),(4), and (5) behave differently.
I think (4) is correct and (3) and (5) are bugs ?

Yakov



I see this behaviour too, with the restriction above, in (g)vim (Huge, GTK2) 
on SuSE Linux, in both GUI and Console modes.



Best regards,
Tony.

long echomsg + 'set shortmess+=T' + norm-vs-without-norm

[Yakov Lerner]

I observe strange behaviour related to 'set shortmess+=T' . Sometimes
this 'T' flag shortens long messages, sometimes it does not.
To see:
1.
vim -u NONE
2.
:set nocp shortmess=aT
:nmap ZB :echomsg repeat('a',&co+10)
3.
Press ZB. You get long message and 'Press Enter' prompt.
4.
Type
:norm ZB
You get shortened message, and no ''Press Enter' prompt.
5.
Type
:echomsg repeat('a',&co+10)
This behaves like (3), not like (4).

I don't understand why (3),(4), and (5) behave differently.
I think (4) is correct and (3) and (5) are bugs ?

Yakov