comp.editors
  Home FAQ Contact Sign in
comp.editors only
 
Advanced search
May 2010
motuwethfrsasuw
     12 17
3456789 18
10111213141516 19
17181920212223 20
24252627282930 21
31       22
2010
 Jan   Feb   Mar   Apr 
 May   Jun   Jul   Aug 
 Sep   Oct   Nov   Dec 
2010 2008 2007 2006
total
comp.editors Profile…
RELATED GROUPS

POPULAR GROUPS

more...

 Up
  Re: vim narrowing to region like emacs         


Author: esquifit
Date: May 13, 2010 10:07

On 28 Abr, 16:26, Christian Brabandt 256bit.org> wrote:
> Anything else, that this plugin should do? (Highlight in the original
> buffer the narrowed region, for example?)

Thanks for this nice piece of code. Two comments:

1) You're using the following to delete the contents of the scratch
buffer
:%%d_
I suppose you meant %%d _ (aka "black hole register". Without the
space between d and _ you are not using the _ register, check
out :registers).

2) I was searching for something like that because I wanted to edit
tables 'inline' and make use of the csv plugin in

http://vim.wikia.com/wiki/Working_with_CSV_files.

I've seen that you have also worked based on that tip to produce

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

Maybe you want to consider merging both scripts into a new "edit
inline tables" script? With "inline table" I mean a 'csv fragment'
surrounded by 'normal' (non-structured) text.
no comments
  VIM question - the "-o" command line option         


Author: Kenny McCormack
Date: May 13, 2010 08:16

I don't think the "-o" (or "-O") command line option works either as it
should or as it is documented. I've often wondered if this is consider
"working as designed", or just a "known bug" (that no one has ever
chosen to spend any time working on) or "what"...

The help file says:

--- Cut Here ---
-o[N] Open N windows, split horizontally. If [N] is not given,
one window is opened for every file given as argument. If
there is not enough room, only the first few files get a
window. If there are more windows than arguments, the last
few windows will be editing an empty file.
{not in Vi}

*-O*
-O[N] Open N windows, split vertically. Otherwise it's like -o.
If both the -o and the -O option are given, the last one on
the command line determines how the windows will be split.
{not in Vi}
--- Cut Here ---
Show full article (1.17Kb)
3 Comments
  [vimhelp-de] merry christmas         


Author: Florian Rehnisch
Date: Dec 26, 2008 01:58

To more files (usr_44, usr_43) and
merry christmas.

http://www.florianrehnisch.de/vimhelp/
no comments
  Want McCain US slave to ISRAEL ?         


Author: akiarmy
Date: Sep 20, 2008 07:53

Want McCain US slave to ISRAEL ?

-----------------------------------------------------------------------------------
Why is McCAIN too obsequious TO ISRAEL ?
---------------------------------------------------------------------------------------

Why we must process 5 Israeli Hebrews ? =
----------------------------------------------------------------------------------------

Why we must process 5 Israeli Hebrews ,
arrested by the Police at 2001, September, 11 , on NYC ?

While each of them had a new last photography of himself, on the
wich he was very very happy,
on the background of WTC 2 towers falling down ?
----------------------------------------------------------------------------------------

*) Because it can be they murdered 3,000 people of America,
on the World Trade Center of America ..

*) Because it can be they were operating,
according to the Same Satanic Center,
Which programmed also the missile against Pentagon.
------------------------------------------------------------------------------------------
After a month, they escaped into Israel, to searching protection !
Show full article (2.20Kb)
no comments
  Re: vim and unicode         


Author: Christoph Spohr
Date: Sep 19, 2008 03:00

Hi Dave,

Dave Feustel wrote:
> How well does vim work with unicode (utf8)? Is there any way to
> use virtual keyboards to facilitate the inclusion of multiple
> languages (eg English, Russian, French) in the same document?
>
> Thanks.

vim has i pretty good support of different keyboards.

My default keyboard is german, for Ancient Greek support I add to
my .vimrc:

set keymap+=greek_utf-8
set imi=0 ims=0 "start with a additional keymap
set but inactive

You can find a supported keympas and their names in the
/usr/share/vim/vim72/keympas folder.

Now vim will start with you default keymappings, in my case utf8
german. If you press in insert (!) mode, vim will switch to
the ancient greek keyboard. You can edit these keymaps to your
liking, the ancient greek keyboard defaults to the Latex-Mappings.
Show full article (1.13Kb)
no comments
  Re: vim and unicode         


Author: Dave Feustel
Date: Sep 18, 2008 12:09

Ben C wrote:
> On 2008-09-13, Dave Feustel mindspring.com> wrote:
>> How well does vim work with unicode (utf8)?
>> Is there any way to use virtual keyboards
>> to facilitate the inclusion of multiple
>> languages (eg English, Russian, French)
>> in the same document?
>
> You don't do that with vim but with whatever your host system provides.
> On GNU/Linux you use something called "xim" or "skim" which has a lot of
> different input methods for all kinds of different languages.
>
> Then you just use it to input characters into vim, and they come up on
> the screen provided you've got the fonts. Vim works pretty well with it
> all, although it doesn't do right-to-left or bidirectional layout for
> things like Arabic, and you would probably need to mess around a bit to
> get gq to work properly for Chinese or Japanese or anything that doesn't
> just break lines basically at spaces.
>
> Russian and French should be no problem though. ...
Show full article (1.15Kb)
no comments
  Aurora Editor (v3.3 beta 1)         


Author: jh
Date: Sep 16, 2008 16:58

How would the following look like if this should work:

The object is to delete all occurrences of one number/word pr. line in the first window in the file
loaded in the next window

function

create _thisBuff // I assume that a buffer has to be created

markword (_thisBuff) // now the word at the cursor should be marked, and then pasted to the
buffer

nextwindow row 1 col 1 // then go to next window upper left corner

find (get _thisBuff) // then the word marked in the previous window should be search for in the new
window (in this example it's just one number at the beginning of the line so there's no need to
specify ''Whole word' or 'Ignore case', or anything like that)

if exist (find) markword delline // and if the word is found the this line should be deleted - if not
exist then do nothing

next window down // then return to the first window and go down one row

// and all this should then repeat as long as there's a next line in the new file to mark a word to find
in the next window

end
Show full article (1.42Kb)
no comments
  vim: "XSMP opening connection"         


Author: Spiros Bousbouras
Date: Sep 15, 2008 14:55

I tried starting vim a little while ago and nothing
happened. I pressed Ctrl-C and it started normally. So I
tried again with
vim -u NONE -V90 file
and got
XSMP opening connection
after which nothing happened. I pressed Ctrl-C and got
XSMP SmcOpenConnection failed: IO error occured opening
connectionOpening the X display failed
Opening the X display took 1 msecOpening the X display took 4 msec
Interrupt: Press ENTER or type command to continue
and then it started normally.
I also tried
DISPLAY= vim -u NONE -V90 file
but it didn't make any difference.
Show full article (1.43Kb)
no comments
  Input vi commands from a file         


Author: angiulillo
Date: Sep 15, 2008 06:04

Hello
I'm working with vi editor to modify some configuration files of an
application and I would know if it is possible to input vi commands
from a file, like .netrc file for ftp application.

Thank you

Angelo
5 Comments
  Re: How do I see unicode characters that look like ascii.         


Author: Mark Healey
Date: Sep 14, 2008 22:09

On Sun, 14 Sep 2008 13:33:21 -0500, dfeustel wrote:
> Mark Healey wrote:
>>
>> I've got a bunch of files with unicode characters that look like ascii
>> characters, such as a non-breaking space and a normal space. I'd like
>> to see them. I seem to remember in an older version or an older
>> configuration I would see something like <##> where ## was some hex
>> digits, although some were all represented with glyphs.
>
> Do you want to see the glyths or the numeric codes?

The numeric codes for everything above 127.

Do you know whether
> the files are encoded with utf8, uf16, or utf32? (My guess is utf8)

utf8

--
Mark Healey
marnkews ãt healeyopolis döt com
1 Comment
1 2 3 4 5 6 7 8 9