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
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
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
-byte text
*new-print-multi-byte*
YL --
YL The |:hardcopy| command now supports printing multi-byte characters.
YL The 'printmbcharset' and 'printmbfont' options are used for this.
YL Also see |postscript-cjk-printing|. (Mike Williams)
As you can see
Mark Manning did utter on 10/09/2006 23:52:
I saw in the c.vim that there was an error statement for octal numbers.
There isn't one for hex numbers so I made one really quickly. If you
want, just put it into the c.vim file. :-)
The test:
syn regioncHexErrorstart=0x\x*[g-zG-Z]
mwoehlke did utter on 11/09/2006 17:44:
Bram Moolenaar wrote:
Mark Manning wrote:
I saw in the c.vim that there was an error statement for octal
numbers. There isn't one for hex numbers so I made one really
quickly. If you want, just put it into the c.vim file. :-)
The test:
syn region
mwoehlke did utter on 11/09/2006 18:37:
Mike Williams wrote:
mwoehlke did utter on 11/09/2006 17:44:
Bram Moolenaar wrote:
I don't know what the rules are in all kinds of C, but at least things
like 0x0L, 0x0u, 0x0UL are valid.
Using a match instead of region would be simpler.
If one takes
Hi,
Attached is a patch to use VC8 specific optimization options. FTR, VC8
no longer supports the /Gn processor code generation directive, and the
makefile now uses link time code generation when not optimizing for space.
Enjoy.
Mike
--
If space is a vacuum, who changes the bags?
***
On 17/01/2007 15:09, A.J.Mechelynck wrote:
Mike Williams wrote:
Hi,
Attached is a patch to use VC8 specific optimization options. FTR, VC8
no longer supports the /Gn processor code generation directive, and the
makefile now uses link time code generation when not optimizing for space
On 17/01/2007 19:44, Bram Moolenaar wrote:
Mike Williams wrote:
Attached is a patch to use VC8 specific optimization options. FTR, VC8
no longer supports the /Gn processor code generation directive, and the
makefile now uses link time code generation when not optimizing for space.
Although
On 18/01/2007 20:55, Bram Moolenaar wrote:
Mike Williams wrote:
Attached is a patch to use VC8 specific optimization options. FTR, VC8
no longer supports the /Gn processor code generation directive, and the
makefile now uses link time code generation when not optimizing for space.
Although
Hi Mathias.
On 20/01/2007 11:48, Mathias Michaelis wrote:
Hi Mike
Thanks a lot for your patch. If the appropriate compiler options are
applied to VC8, the make_mvc.mak script emits much less warning
messages, and probably the created binary is better optimised in
some manner.
Alas, your patch
Hi again,
Attached is a new version of the VC makefile that uses MSVCVER if
defined or derives a value from nmake. This should allow the file to be
used straight from a source download without any environment variables
having to be set.
If anyone has other values for _NMAKE_VER (just run
from
Alexei Alexandrov and Mike Williams
Last week's service pack for VS2005 has changed the nmake version
number. It just needs the following three lines adding after the ones
for the previous version for VS2005.
!if $(_NMAKE_VER) == 8.00.50727.762
MSVCVER = 8.0
!endif
I also had to edit
On 19/03/2007 17:39, David Brown wrote:
Martin Krischik wrote:
Am Montag 19 März 2007 schrieb David Brown:
A macro like this:
#define FOO ((fooy) { field: 4 })
Whenever I thougth I saw it all C comes with another suprise. What
the heck is this good for?
It is a constant structure,
On 18/05/2007 03:31, A.J.Mechelynck wrote:
:set enc? penc?
encoding=utf-8
printencoding=utf-8
:%ha
not found in runtimepath: print/utf-8.ps
Is this last message normal?
Yes.
I have here a file including an Esperanto-French glossary, which contains both
the consonants+circumflex of
16 matches
Mail list logo
