AltME groups: search

Well, ^I is a control-i.. and in vim, that inserts a tab.  ^- is 
the tab character in Rebol

This is how vim color REBOL code: http://home.tiscali.dk/john.niclasen/rebol/color-test-vim.html

I programmed in COBOL for many years without coloring. Then I started 
using vim, and I found, it looked weird with all those colors. After 
a while, I started to really like it, because it's so much easier 
to read the code. Colors make our brains look and distinguish components 
much better than words. I'm for colors. But they have to be balanced, 
so it doesn't hurt the eyes too much.

I prefer the color-code scheme over the VIM scheme (don't like the 
pink), but as long as it isn't too bright most anything should be 
OK. 


It would be interesting to do some research on using different rendering 
schemes for code, based on activity. For example, when writing and 
maintaining code, I like comments in gray, so they "fade out" a bit; 
but if you're reading code, in a Literate Programming sense, you 
probably want the prose to stand out and the code to be subordinate.

Vim and Editor² display the chars incorrectly.
Notepad++ shows the chars correctly.

Vim supports unicode and on my system shows the characters correctly.

Anton: you're right Vim does display the file correctly, although 
not by default. I guess it helps when you read the manual. :-)

swall, yes, strange, I can't remember configuring vim for utf-8 (I 
don't use it regularly), but it displayed correctly straight away 
for me. Must be some dark config option or something...

(Working on rebol-helper functionality for Vim)

@Pekr: I use the vi editor (now mostly vim) to write code, and it 
allow me to set auto-indent, so when I start something indented, 
it'll stay indented, when I go to next line. Further indenting is 
done by inserting a <tab>, and going back is done with <backspace>. 
So it's no big problem for me to write code indented as makedoc require.

About *bold*, ~italic~, -strike- and _underline_, maybe it would 
be a good idea to introduce a new paragraph level state change called 
=magic (I got the idea from the vim editor). If the writer type:

=magic


then the short form of bold, italic and so can be used. If the writer 
type:

=/magic


we're back to the default character level state changes: [b], [i], 
[s] and [u]. Isn't that a good idea? :-)

50mb and includes.. 


XMMS (MP3, CD Music, and MPEG), FTP client, Dillo web browser, links 
web browser, FireFox, spreadsheet, Sylpheed email, spellcheck (US 
English), a word-processor (FLwriter), three editors (Beaver, Vim, 
and Nano [Pico clone]), graphics editing and viewing (Xpaint, and 
xzgv), Xpdf (PDF Viewer), emelFM (file manager), Naim (AIM, ICQ, 
IRC), VNCviwer, Rdesktop, SSH/SCP server and client, DHCP client, 
PPP, PPPoE (ADSL), a web server, calculator, generic and GhostScript 
printer support, NFS, Fluxbox window manager, games, system monitoring 
apps, a host of command line tools, USB support, and pcmcia support, 
some wireless support.

g~$ in vim, to switch case for everything from the cursor to the 
end of line

another thing that has been *really* great is using vim vertical 
split after stretching it to cover both monitors :-) eg. vimdiff. 
it does not even compare to using it on a single monitor where you 
see only half of the line.

vim

It seems to work without the newlines, but then the ps file become 
difficult to enter with e.g. vim. That part is fast, I think. It 
only put in a newline for every 80 chars.