Hi Zyx, pribiet :)

On Nov 9, 9:47 pm, ZyX <[email protected]> wrote:
> Reply to message «Re: no echo output in command line»,
> sent 20:33:36 09 November 2010, Tuesday
> by rameo:
>
>
> It should be a vim bug, but I failed to reproduce this behavior. Have you
> removed old (set enc) or new (e ++enc) encoding lines? And what is your vim
> version?
>


Vim Version 7.3.46

When I disable the encoding lines the script gives an echo output.

  function! s:NonPrintable()
      "setlocal enc=utf8
      if search('[^\x00-\xff]') != 0
        call matchadd('Error', '[^\x00-\xff]')
        echo 'Non printable characters in text'
      else
       "setlocal enc=latin1
        echo 'All ok'
      endif
  endfunction

Now there is an echo output.

> > Same here. In latin1 I can print fine.
> > In utf8 not.
> > I have to remove/modify all non latin1 characters before printing.
>
> You should be able to print even in utf-8, but all characters that cannot be
> converted to latin1 will be replaced.
>

True.

> > You also do not print in Vim???
> > Why so many people do not print in Vim?
> > Is there no way to make printing interesting enough to print in Vim
> > self?
>
> Because vim has lots of problems with printing coming from the time when you 
> can
> hardly imagine coloured printing of triple integral sign (problems both with
> colours and multibyte characters, latter occures in other places too). Try
> printing from kate (it is a good KDE editor), it will save all colours and 
> print
> all characters that are supported by your font. If you use vim, the only thing
> you can do is to use some convert-to-html plugin and print the result of its
> work (it is even mentioned just above the `:hardcopy' tag in `:h :hardcopy').
>

Ok.

> > I've already tried this one a few days ago. It opened all my (latin1)
> > files in utf8 and corrupted a few one after saving.
>
> It should not: latin1 file is not a valid UTF-8 file.
>
> > You ask me about printencoding in your other message.
> > No output echoing it.
> > (printencoding is only available when compiled with the |+printer| and
>
> > |+postscript| features, not in gvim. I use gvim}
>
> I do not see why gvim cannot have `+printer' feature. I compile development
> version with
>     ./configure --with-features=huge
>     make
> and resulting vim executable has both gtk graphics and printer support. If you
> want to see, whether you have printencoding option, use either
>     echo has("postscript")
>

echo has("postscript") ---> 0


>     echo exists('&printencoding')

echo exists('&printencoding') ---> 1


> . If you have not modified your `printencoding' then it is empty and
>     echo &printencoding


echo &printencoding ---> nothing echoed.

> will not echo anything. If you have printer support disabled, then it will 
> echo
> `E113' error, not nothing.
>
> > There is also another annoying thing, when printing in gvim, the text
> > has to be formatted before printing, if not it breaks in the middle of
> > words.
>
> Just another reason why one should not print from vim.
>

You are all working so long with VIM, Bram and the others.. no one is
enable to resolve these problems?

Kind regards,
Rameo

-- 
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

Reply via email to