Ilya | 1 Sep 08:36 2006

Re: Fixing cweb.vim

David Brown wrote:
> I'm trying to get cweb.vim to work better, and am not sure how to go 
> about this.
>
> Most of a cweb file is regular TeX (or LaTeX), with some occasional 
> regions
> that are C code.  The way it is implemented now, works with simple
> constructs.
>
> However, tex.vim frequently will enclose large sections of the document
> within a region and the cweb.vim which the webCRegion is not part of.
>
> I think I can fix this by adding an appropriate containedin=... field to
> the definition of webCRegion.
>
> What I'm having difficulty with is figuring out what to put there.  Is
> there a way of finding out what region a given part of the buffer is in?
 From :help synID

        Example (echoes the name of the syntax item under the cursor): >
            :echo synIDattr(synID(line("."), col("."), 1), "name")
>
> Thanks,
> David Brown
>
>
>

Alexey I. Froloff | 1 Sep 15:33 2006
Picon

[PATCH] russian vimtutor is b0rken in UTF-8 locale

Quick solution: generate tutor.ru.utf-8 from tutor.ru (KOI8-R).
This will work right now.

Better solution: keep tutor.ru.utf-8, generate .cp1251 and .koi8
from it and detect all encodings in tutor.vim.  vimtutor will
fall back to english in "unsupported" locales (ru_RU.ISO8859-5)
for example.

Attached patch for quick solution.  Better solution can wait till
7.1.  When, by the way?

--

-- 
Regards,
Sir Raorn.
diff -cdrN ../vim70-orig/runtime/tutor/Makefile runtime/tutor/Makefile
*** ../vim70-orig/runtime/tutor/Makefile	Mon Jun  7 18:32:39 2004
--- runtime/tutor/Makefile	Fri Sep  1 17:21:29 2006
***************
*** 3,9 ****
  # The Japanese tutor exists in three encodings.  Use the UTF-8 version as the
  # original and create the others with conversion.

! all: tutor.ja.sjis tutor.ja.euc tutor.ko.euc

  tutor.ja.sjis: tutor.ja.utf-8
  	nkf -WXs tutor.ja.utf-8 > tutor.ja.sjis
--- 3,9 ----
  # The Japanese tutor exists in three encodings.  Use the UTF-8 version as the
(Continue reading)

Alexey I. Froloff | 1 Sep 15:35 2006
Picon

Re: Bad QUOTESED expression in src/Makefile

* Alexey I. Froloff <raorn <at> > [060831 01:27]:
> I think QUOTESED should look like:

> QUOTESED = sed -e 's/[\\"]/\\&/g' -e 's/\\"/"/' -e 's/\\";$$/";/'

Patch attached.

-- 
Regards,
Sir Raorn.
diff -cdrN ../vim70-orig/src/Makefile src/Makefile
*** ../vim70-orig/src/Makefile	Fri Sep  1 17:18:36 2006
--- src/Makefile	Fri Sep  1 17:34:02 2006
***************
*** 2206,2212 ****
  auto/osdef.h: auto/config.h osdef.sh osdef1.h.in osdef2.h.in
  	CC="$(CC) $(OSDEF_CFLAGS)" srcdir=$(srcdir) sh $(srcdir)/osdef.sh

! QUOTESED = sed -e 's/"/\\"/g' -e 's/\\"/"/' -e 's/\\";$$/";/'
  auto/pathdef.c: Makefile auto/config.mk
  	- <at> echo creating $ <at> 
  	- <at> echo '/* pathdef.c */' > $ <at> 
--- 2206,2212 ----
  auto/osdef.h: auto/config.h osdef.sh osdef1.h.in osdef2.h.in
  	CC="$(CC) $(OSDEF_CFLAGS)" srcdir=$(srcdir) sh $(srcdir)/osdef.sh

! QUOTESED = sed -e 's/[\\"]/\\&/g' -e 's/\\"/"/' -e 's/\\";$$/";/'
  auto/pathdef.c: Makefile auto/config.mk
(Continue reading)

Benji Fisher | 1 Sep 21:10 2006

Re: Fixing cweb.vim

On Fri, Sep 01, 2006 at 09:36:55AM +0300, Ilya wrote:
> David Brown wrote:
[...]
> >However, tex.vim frequently will enclose large sections of the document
> >within a region and the cweb.vim which the webCRegion is not part of.
> >
> >I think I can fix this by adding an appropriate containedin=... field to
> >the definition of webCRegion.
> >
> >What I'm having difficulty with is figuring out what to put there.  Is
> >there a way of finding out what region a given part of the buffer is in?
> From :help synID
>       
>        Example (echoes the name of the syntax item under the cursor): >
>            :echo synIDattr(synID(line("."), col("."), 1), "name")

     IIUC, synIDattr() always returns a syn-match or syn-keyword group.
It does not tell you whether you are in a syn-region.

HTH					--Benji Fisher

Bram Moolenaar | 1 Sep 22:18 2006
Picon
Picon

Vim BOF session


Greetings, Vim users.

I am hosting a Vim BOF at the upcoming O'Reilly Open Source Convention:

      Title: Vim 8?
       Date: Tuesday, 19 September 2006
       Time: 20:30 - 21:30
   Location: Salon Versailles

    Summary: Vim 7 was released May 2006. Does it make sense to make
             another major release and add lots of new features? Or
             should priority be given to fix problems and fine tune
             existing features?

             What new features would users really profit from? Talk
             about the pros and cons with the main Vim author.

The conference is held in Brussels, 18 - 21 September.

More information: http://conferences.oreillynet.com/cs/euos2006/view/e_sess/9854

--

-- 
Linux is just like a wigwam: no Windows, no Gates and an Apache inside.

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- 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    ///

(Continue reading)

Bram Moolenaar | 1 Sep 22:18 2006
Picon
Picon

Re: [PATCH] russian vimtutor is b0rken in UTF-8 locale


Alexey Froloff wrote:

> Quick solution: generate tutor.ru.utf-8 from tutor.ru (KOI8-R).
> This will work right now.
> 
> Better solution: keep tutor.ru.utf-8, generate .cp1251 and .koi8
> From it and detect all encodings in tutor.vim.  vimtutor will
> fall back to english in "unsupported" locales (ru_RU.ISO8859-5)
> for example.

I checked the existing Russian tutor files, and they are exactly the
same when converted to utf-8.  Thus we can use the utf-8 file as the
master and generate the others from it.

I'll include your change to tutor.vim.

> Attached patch for quick solution.  Better solution can wait till
> 7.1.  When, by the way?

No idea when there will be a 7.1 version.  I still have lots of fixes in
the todo list.

--

-- 
The greatest lies of all time:
  (1) The check is in the mail.
  (2) We have a really challenging assignment for you.
  (3) I love you.
  (4) All bugs have been fixed.
  (5) This won't hurt a bit.
(Continue reading)

Bram Moolenaar | 1 Sep 22:18 2006
Picon
Picon

Re: session-file problem in presence of 'set acd'


Yakov Lerner wrote:

> When 'acd' is set, 'vim -S' open files in wrong directory.
> To reproduce:
> 
> 1. make your ~/.vimrc 1-liner 'set acd'
>    (Alternatively, use use "vim -u NONE -c 'set acd'" instead of vim
> in commands below).
> 2. vim ~/xxx            # or
> :he options.txt
>             " now you have two files open: (1) ~/xxx (2)
> $VIMRUNTIME/doc/options.txt
> :mksession! /tmp/3
> :q!
> 3. vim -S /tmp/3
> 4. You'll see that buffer 'options.txt' is empty.
> ':pwd' in window of options.txt shows that current directory is incorrect.
> 
> The problem is that ':edit' commands in session-file do not
> contain full paths. Incomplete paths do not work when 'acd' is set.
> Here are relevant lines from sessionfile, the /tmp/3:
> 
>    cd /usr/local/share/vim/vim70/doc
>    edit ~/xxx
>    edit options.txt
> 
> This (3rd line)does not work with 'set acd'. I think all filenames
> must be with full path like
> 
(Continue reading)

Bram Moolenaar | 1 Sep 22:18 2006
Picon
Picon

Re: Bad QUOTESED expression in src/Makefile


Alexey Froloff wrote:

> There is QUOTESED expression for creating auto/pathdef.c:
> 
> QUOTESED = sed -e 's/"/\\"/g' -e 's/\\"/"/' -e 's/\\";$$/";/'
> ...
>    <at> echo 'char_u *default_vim_dir = (char_u *)"$(VIMRCLOC)";' | $(QUOTESED) >> $ <at> 
> 
> However:
> 
> gcc -c -I. -Iproto -DHAVE_CONFIG_H     -pipe -Wall -O2 -march=pentium4
-DSYS_VIMRC_FILE=\"/etc/vim/vimrc\" -DSYS_GVIMRC_FILE=\"/etc/vim/gvimrc\"         -o
objects/pathdef.o auto/pathdef.c
> auto/pathdef.c:7: error: 'etc' undeclared here (not in a function)
> auto/pathdef.c:7: error: 'vim' undeclared here (not in a function)
> auto/pathdef.c:7: error: stray '\' in program
> auto/pathdef.c:7: error: stray '\' in program
> auto/pathdef.c:7: error: 'vimrc' undeclared here (not in a function)
> auto/pathdef.c:7: error: expected ',' or ';' before string constant
> auto/pathdef.c:7: error: stray '\' in program
> auto/pathdef.c:7: error: stray '\' in program
> 
> $ grep all_cflags auto/pathdef.c
> char_u *all_cflags = (char_u *)"gcc -c -I. -Iproto -DHAVE_CONFIG_H     -pipe -Wall -O2 -march=pentium4
-DSYS_VIMRC_FILE=\\"/etc/vim/vimrc\\" -DSYS_GVIMRC_FILE=\\"/etc/vim/gvimrc\\"      
> 
> I think QUOTESED should look like:
> 
> QUOTESED = sed -e 's/[\\"]/\\&/g' -e 's/\\"/"/' -e 's/\\";$$/";/'
(Continue reading)

Bram Moolenaar | 1 Sep 22:18 2006
Picon
Picon

Re: vim mailing lists


Gautam Iyer wrote:

> On Wed, Aug 30, 2006 at 10:12:44PM +0200, Bram Moolenaar wrote:
> 
> > > > Apparently the sorbs blacklist mechanism is still being used, causing
> > > > trouble for some people.  I have asked the mail server maintainer to
> > > > remove sorbs a few times now...
> > > 
> > > Twice recently, sorbs has bounced my mails to the list because some
> > > server between my ISP and the vim-dev list is on its blacklist.
> > > 
> > > Do you have any plans to move the vim mailing lists to a new server,
> > > where you (or someone more responsive) has administrative control?
> > 
> > The plan was to move the maillists to the server that is now already the
> > Vim mail server.  And the one causing this blacklist trouble...
> > 
> > There is no progress in moving the maillists.  I suppose it's time to
> > find a better place for the Vim mail server.  Instead of a server that
> > just happens to be available and run by someone who doesn't always
> > respond, or some big and anonymous server park like Yahoo, I think we
> > should look for a small site that does have 24 hour support.
> 
> How about the sourceforge mailing lists? I know sourceforge has had
> numerous failures in the past. But I think their mailing lists might be
> OK.

Features missing (at least):
- When someone is not subscribed the message should bounce, not sent to
(Continue reading)

Yakov Lerner | 1 Sep 22:22 2006
Picon

Re: session-file problem in presence of 'set acd'

On 9/1/06, Bram Moolenaar <Bram <at> moolenaar.net> wrote:
>
> Yakov Lerner wrote:
>
> > When 'acd' is set, 'vim -S' open files in wrong directory.
> > To reproduce:
> >
> > 1. make your ~/.vimrc 1-liner 'set acd'
> >    (Alternatively, use use "vim -u NONE -c 'set acd'" instead of vim
> > in commands below).
> > 2. vim ~/xxx            # or
> > :he options.txt
> >             " now you have two files open: (1) ~/xxx (2)
> > $VIMRUNTIME/doc/options.txt
> > :mksession! /tmp/3
> > :q!
> > 3. vim -S /tmp/3
> > 4. You'll see that buffer 'options.txt' is empty.
> > ':pwd' in window of options.txt shows that current directory is incorrect.
> >
> > The problem is that ':edit' commands in session-file do not
> > contain full paths. Incomplete paths do not work when 'acd' is set.
> > Here are relevant lines from sessionfile, the /tmp/3:
> >
> >    cd /usr/local/share/vim/vim70/doc
> >    edit ~/xxx
> >    edit options.txt
> >
> > This (3rd line)does not work with 'set acd'. I think all filenames
> > must be with full path like
(Continue reading)


Gmane