From: Sime Ramov, Sep 7, 2004 5:22 AM
> On Mon, 06 Sep 2004 21:50:38 -0400, Steve Hall wrote:
> > Now that I think about it, this should work only only when you
> > create a new file (File > New), but not the first buffer you see
> > at start up.
> No, it does not work. I will try with latest beta.
I ran some tests, and here is what worked for me, in cream-user.vim:
" ensure buffers are always unix format
" get buffer number
let mybufnr = bufnr("%")
" only if buffer is unnamed and doesn't exist
if bufname(mybufnr) == ""
\&& bufexists(mybufnr) == 1
" remember unmodified state
if getbufvar(mybufnr, "&modified") == 0
let mod = 1
" set the fileformat to unix
" recover unmodifed state
autocmd VimEnter,BufEnter * call Cream_fileformat_unix()
> > You're using a font that does not support the character being
> > selected by Cream. What do the following lines produce on your
> > system:
> No, I am using Lucida Console, but when the encoding is default
> (cp1250) then it's ok, but when I change default file encoding to
> utf-8, then it's messed up.
I can see it now. This appears to be a limitation of the OS to
represent some utf8 characters, something we could easily work around.
But unfortunately, the ellipses ("..." as one character) is not
available, so we'll need to use an underscore "_".
Try this: replace your existing file of the same name with the one
attached. Then put these two lines in your cream-user.vim:
Does that work?
Steve Hall [ digitect@... ]
Cream... sheep clothing for the Vim text editor!