Re: 7.0.188 - problem with directory browser?

2007-01-29 Thread Charles E Campbell Jr

Denis Perelyubskiy wrote:


in version 7.0.188 (I am on windows xp, us) nothing works when I select
'..' when browsing a directory. has anyone seen this? is this something
peculiar to my installation, a bug, or a feature?

 


I suspect that you need a recent version of netrw.

To get an up-to-date version of netrw, you'll also need to get an 
up-to-date version of vimball.  So:


1) Get up-to-date versions of vimball and netrw:

  vimball:
http://vim.sourceforge.net/scripts/script.php?script_id=1502
 -or-   http://mysite.verizon.net/astronaut/vim/index.html#VimBall
 (the mysite.verizon.net one will be the more recent version)

  netrw:
http://vim.sourceforge.net/scripts/script.php?script_id=1075
 -or-   http://mysite.verizon.net/astronaut/vim/index.html#NETRW

2) Remove the old vimball plugin and install the new one:

   Linux:
   cd /usr/local/share/vim/vim70
   /bin/rm plugin/vimball*.vim autoload/vimball*.vim doc/pi_vimball.txt
   mv (wherever it was downloaded)/vimball.tar.gz .
   gunzip vimball.tar.gz
   tar -xvf vimball.tar

   Windows:
   Under Windows, check your runtimepath to determine where your 
vim 7.0's runtime directories are:


   vim
   :echo rtp
   :q

   The first directory is likely your personal plugins directory, 
the second one is your vim system directory.


   cd (to your vim system directory)
   del plugin\vimballPlugin.vim
   del autoload\vimball.vim
   del doc\pi_vimball.txt
   ren (wherever)\vimball.tar.gz vimball.tar.gz
   gunzip vimball.tar.gz
   tar -xvf vimball.tar

3) Remove system version of netrw:
 
   Linux:

   cd /usr/local/share/vim/vim70
   /bin/rm plugin/netrw*.vim autoload/netrw*.vim doc/pi_netrw.txt 
syntax/netrw*.vim
  
   Windows:

   cd (to your vim system directory)
   del plugin\netrwPlugin.vim
   del autoload\netrw.vim
   del doc\pi_netrw.txt
   del syntax\netrw.vim

4) Install an up-to-date version of netrw:
  vim netrw.vba.gz
  :so %
  :q

Regards,
Chip Campbell




Re: BOF Vim 8 - EncryptLine

2007-01-29 Thread Charles E Campbell Jr

Matthew Winn wrote:


Text editors don't do encryption and never should.
   



How else would you ensure that you can have encrypted text _without_
the need to temporarily store a plaintext copy of the file?
 



Pipe the text through to an external encryption tool, such as pgp.
Assuming your o/s supports true pipes...

Chip




for vim v8: how about keepundo ?

2007-01-29 Thread Charles E Campbell Jr
The idea would be to leave the undo list alone, so that when the undo 
table gets updated next it'll have a bigger change.


Regards,
Chip Campbell



Re: Odp: BOF Vim 8 - Suggestions

2007-01-29 Thread Alexei Alexandrov
Hi Stefano Zacchiroli, you wrote:

 
 The solution of being compatible when invoked as 'vi' and being
 nocompatible when invoked in a different way made everybody happy. The
 (trivial) patch we are using to implement this behaviour is available
 at:
 
   
 http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim/debian/tiny/vimrc.tiny.diff?op=filerev=0sc=0
 
 FWIW we also set a lot of other default values when not invoked as 'vi'.
 

This really seems to be a good option.

-- 
Alexei Alexandrov


Re: BOF Vim 8 - Suggestions

2007-01-29 Thread Alexei Alexandrov
Hi Bram Moolenaar, you wrote:

 
 To finish, I'm not suggesting that the optimum one-size-fits-all set
 of mappings be determined. Any set of well-planned mappings
 would be better than the current blank slate.
 
 The best set of mappings is what you make yourself.  That's like: don't
 give a hungry person food, teach him how to grow food.
 

Sort of OT but still: before teaching it's better to give them some food - 
otherwise they will die before they even learn anything...

-- 
Alexei Alexandrov


Re: for vim v8: how about keepundo ?

2007-01-29 Thread Nikolai Weibull

On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:

The idea would be to leave the undo list alone, so that when the undo
table gets updated next it'll have a bigger change.


What do you mean?  From the very short description it sounds like your
describing :undojoin.

 nikolai


Re: for vim v8: how about keepundo ?

2007-01-29 Thread Charles E Campbell Jr

Nikolai Weibull wrote:


On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:


The idea would be to leave the undo list alone, so that when the undo
table gets updated next it'll have a bigger change.



What do you mean?  From the very short description it sounds like your
describing :undojoin.


A keepundo would be more akin to the keepjumps, keepalt style of 
suppressing

some update for the command which follows.

Regards,
Chip Campbell



Re: for vim v8: how about keepundo ?

2007-01-29 Thread Nikolai Weibull

On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:


Nikolai Weibull wrote:



 On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:



  The idea would be to leave the undo list alone, so that when the undo
  table gets updated next it'll have a bigger change.



 What do you mean?  From the very short description it sounds like your
 describing :undojoin.



A keepundo would be more akin to the keepjumps, keepalt style of
suppressing
some update for the command which follows.


But to be able to undo/redo, Vim has to know about what changes have
taken place, otherwise it can't guarantee that undo/redo will work
correctly.

 nikolai


Re: for vim v8: how about keepundo ?

2007-01-29 Thread A.J.Mechelynck

Nikolai Weibull wrote:

On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:


Nikolai Weibull wrote:



 On 1/29/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:



  The idea would be to leave the undo list alone, so that when the undo
  table gets updated next it'll have a bigger change.



 What do you mean?  From the very short description it sounds like your
 describing :undojoin.



A keepundo would be more akin to the keepjumps, keepalt style of
suppressing
some update for the command which follows.


But to be able to undo/redo, Vim has to know about what changes have
taken place, otherwise it can't guarantee that undo/redo will work
correctly.

 nikolai



IIUC what Dr.Chip said in his original post, the idea is to have the same 
set of changes to undo, but with more of them grouped under a single execution 
of undo/redo (i.e., make the undo points farther away from each other than 
they would be otherwise).


I'm not sure how I feel about this suggestion. I guess the pros and cons would 
have to be discussed in detail.



Best regards,
Tony.


Vim8 idea: complete strings

2007-01-29 Thread Martin Stubenschrott
I often want to complete full strings in quotes (foo, 'bla',
`command bla blub`).

But for now, I really need to type all these things again and again. It
would be nice, if I could say fc-x-c- to complete full strings.
Or maybe also c-xc-' for single qouted strings, and c-xc-` for
`-quoted strings. Or maybe just one command to complete all strings, and
get from context, if we want to complete  ' or ` strings, depending on
what character is in front of c-xc-?. fc-xc-? would complete 
quoted strings 'c-xc-? '-quoted and so on.

--
Martin


Re: Vim8 idea: complete strings

2007-01-29 Thread A.J.Mechelynck

Martin Stubenschrott wrote:

I often want to complete full strings in quotes (foo, 'bla',
`command bla blub`).

But for now, I really need to type all these things again and again. It
would be nice, if I could say fc-x-c- to complete full strings.
Or maybe also c-xc-' for single qouted strings, and c-xc-` for
`-quoted strings. Or maybe just one command to complete all strings, and
get from context, if we want to complete  ' or ` strings, depending on
what character is in front of c-xc-?. fc-xc-? would complete 
quoted strings 'c-xc-? '-quoted and so on.

--
Martin



Note: It is not always easy to determine (except by relying on syntax groups, 
which can be mis-synchronized, unless we use :syn sync fromstart which can 
be unduly slow) whether a given occurrence of  or ' anywhere in the text 
being copied from is an opening or closing quote. Even « is an opening quote 
in French, closing in German, and vice-versa for ».



Best regards,
Tony.


Vim 8.0 Suggestion

2007-01-29 Thread Robert Lee
I'd like to see an external .vimrc editor shipping with gVim and 
directly accessible from within easy mode (e.g. on the tools menu). The 
editor would likely be a totally separate binary though, so maybe a 
separate project is called for.


What I have in mind is a tabbed dialog (depending on platform), that 
behaves like any native dialog on the target platform. So under windows 
you would have OK, Apply and Cancel (assuming that applying .vimrc 
changes to an active vim window is even possible). Only the most basic 
settings would be provided (obviously). This is intended for users 
absolutely new to gVim. Tabs might include:


- Shortcuts (mappings), grouped by mode, sorted by keystrokes
- Abbreviations, similar to above (a.k.a. Auto-correct or Auto-complete)
- Per-language settings (smartindent, formatoptions, textwidth)
- Appearance (colors, fonts, line numbering, titlebar text, tabbar 
text, status bar text, window chrome features)

- Syntax Highlighting Colors (a.k.a. a colorscheme editor)
- Behaviors (search behavior, mouse behavior, command history, scroll 
offset, foldmethod, etc)


Also, it would be nice to have native Win32 help (chm). This would annoy 
most of us but new users would really like to see this I think. Again, 
this can be an external project.


Also, a real built in file browser would be nice (e.g. a sidebar similar 
to that in EasyEdit). Actually an optional Browser Tabpage showing a 
Windows Explorer-like view would be killer on Win32. Oh, and the ability 
to add a New Tab button to the tab bar. Double-clicking does not work 
properly when you are using a text-mode tab bar.


Just brainstorming.

-Robert


Re: JavaScript indentation

2007-01-29 Thread Bram Moolenaar

Martin Stubenschrott wrote:

 On Sun, Jan 28, 2007 at 01:12:00AM +0100, Bram Moolenaar wrote:
   Hope that gets added to the default vim 7.1 distribution, because it's
   quite the best working omni complete script I have seen so far.
  
  Can you mention on what points cppcomplete.vim works better than the
  ccomplete.vim scripts?
  
  If it's overal better I can replace the script.
 
 First, it checks return types of functsion (where possible).
 Lets assume this C code:
 
 typedef struct POINT
 {
   int x;
   float y;
 } _POINT;
 
 
 POINT func()
 {
   // POINT foo = ...
   return foo;
 }
 
 int main()
 {
   func().c-xx-o
 }
 ---
 cppcomplete lists me:
 x and y as members since func() returns a struct of type POINT.
 
 ccomplete does nothing but searching for a long time. I have a 125MB
 tags file in /usr/include with --foldcase, but cppcomplete is instant,
 and ccomplete takes some seconds, and still doesn't find something.
 
 Second, I am not sure, if ccomplete can follow typedefs, cppcomplete can.
 
 These are my main 2 concerns, and probably a unified codebase for c/c++
 completion is easier to maintain. But I have not worked with ccomplete
 that much, so please check, if cppcomplete also works for your usage
 szenarios when coding C.

OK.

Which script are you talking about exactly?  There are four script
matches for cppcomplete on www.vim.org.

-- 
hundred-and-one symptoms of being an internet addict:
65. The last time you looked at the clock it was 11:30pm, and in what
seems like only a few seconds later, your sister runs past you to
catch her 7am school bus.

 /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///