Re: vim | editing pdf files with vim

2006-10-10 Thread Mike Williams

Nikolaos A. Patsopoulos did utter on 10/10/2006 14:58:

Hi all,

is there a way to edit pdf files with vim? If not pdf as is, then eps or 
postscript? I tried with either format but the text kept been converted 
to sthl ike ASCII code.


In general trying to edit PDF or PostScript files is a non-starter, 
unless you have a lot of knowledge about how the files were constructed. 
 In particular, text depends on the font encoding used.  It will be 
much easier to go back to the original application that generated the 
PDF/PS and edit the document there.


TTFN

Mike
--
Free the bound periodicals!


Re: Printing with linebreak

2006-06-22 Thread Mike Williams

Java Bob did utter on 22/06/2006 15:00:

Thanks Jürgen, but your reply does not help.

Your solution
  :set printoptions+=wrap:y

is equivalent to
  :set wrap


I am still looking for something like
 :set linebreak

The problem is th
at my words are b
eing wrapped in t
heir middle!!!


hardcopy does not do linebreak.  It is on the todo list I believe.

Mike
--
Ghosts love music - especially haunting melodies!



Re: how to detect c99 vs c89 (//-comments vs /*-comments)

2006-06-21 Thread Mike Williams

Hi,

In general you cannot detect which version of the standard some C has 
been written against since C89 code should still compile with a C99 
compiler.  There are new keywords, but some developers use macros to 
emulate C99 like features in C89 code.  Your best bet is a mode line, 
possible a good ol' human one as a comment at the top of the file - /* 
This file developed against C99/C89 [delete as applicable] */ - so that 
the code is self documenting, and it can be picked up by VIM on loading 
to set whatever settings you want.



While not helping with detecting whether C source is C89 or C99, my 
alternate C syntax file helps with developing portable C for a 
particular C standard.


http://www.vim.org/scripts/script.php?script_id=234



TTFN

Mike
--
Pulse not found: (A)bandon hope, (R)eincarnate, or (I)gnore?


Re: to get rid of postscript on windows

2006-06-01 Thread Mike Williams

Zbigniew Kowalski did utter on 01/06/2006 14:26:
I'm running Vim 70 on win XP, 
since the upgrade to 70 I can't print because Vim uses postscript mode 
to make a hardcopy (it says "sending to printer" and "print job sent")

and the result gets lost someplace.

The question is: 


1. How to make Vim print using standard windows mode
(with a dialog for selecting a printer and w/o postscript).

2. Why VIM 70 uses postscript rather than normal windows mode? 
Have I done something wrong while I was installing VIM?


3. Is it possible to use postscript mode successfully under win
with a postscript printer, but over the network?


By default VIM on Windows uses the Windows print APIs, it will only 
generate PostScript if it was compiled in.  Does the output from 
:version include +postscript?  If it does then whoever built your 
version of VIM included it, and you need to find another Windows 
distribution that does not include PostScript.


TTFN

Mike
--