Re: [Fwd: [Fwd: Latex Suite - question about font shortcut FMD]]
* Robert Cussons on Wednesday, April 18, 2007 at 09:22:13 +0200:
I work with a nuclear physics model called FMD, so as you can imagine,
each time I type FMD I would prefer it if latex suite didn't interpret
that as an abbreviation for \textmd{}++ :-)
I found the following lines in the wizardfuncs.vim from line 308 onwards:
Font shortcuts {{{
let g:fontshortcuts = ''
\.\n Font shortcuts
\.\n mapleader is a value of g:Tex_Leader
\.\n Shortcuts Effects
\.\n IvV Iv V
\.\n FBF .g:Tex_Leader.bf \\textbf{} {\\bfseries }
\.\n FMD .g:Tex_Leader.md \\textmd{} {\\mdseries }
\.\n
\.\n FTT .g:Tex_Leader.tt \\texttt{} {\\ttfamily }
\.\n FSF .g:Tex_Leader.sf \\textsf{} {\\sffamily }
\.\n FRM .g:Tex_Leader.rm \\textrm{} {\\rmfamily }
\.\n
\.\n FUP .g:Tex_Leader.up \\textup{} {\\upshape }
\.\n FSL .g:Tex_Leader.sl \\textsl{} {\\slshape }
\.\n FSC .g:Tex_Leader.sc \\textsc{} {\\scshape }
\.\n FIT .g:Tex_Leader.it \\textit{} {\\itshape }
}}}
Can I remove this particular functionality by putting a before the
line to do with FMD? So that it would read:
\.\n FMD .g:Tex_Leader.md\\textmd{} {\\mdseries }
does this have the desired effect of commenting this out?
You could just try ;)
Do I need to do anything else, or will this automatically take effect
next time I open a .tex file.
Commenting out line 112 in elementmacros.vim does it for me:
call SIDTex_FontFamily(FMD,series)
c
--
Vim plugin to paste current GNU Screen buffer in (almost) any mode:
http://www.vim.org/scripts/script.php?script_id=1512
Re: invoking yanked register into colon command
* Guillaume Bog on Saturday, March 31, 2007 at 23:04:34 +0800: I getting used to many vim features but I still lack some skills, even after having read the user-manual. For example, I do often want to replace a name in the text with another. What I used to do is selecting it with mouse and type :%s/ctrl-ins/newname/gc Is there a way to do this with the mouse (and without retyping the name) ? What I want is maybe something like 'invoking a yanked register in my colon command' :help c_CTRL-R c -- Vim plugin to paste current GNU Screen buffer in (almost) any mode: http://www.vim.org/scripts/script.php?script_id=1512
Re: python omnicompletion with Python 2.5
* Christian Ebert on Tuesday, March 27, 2007 at 01:15:20 +0200:
I did a few experiments.
As I compile with --disable-darwin, I build a Vim.app (that's how
it's called on the Mac) for testing, and there things get even
more confusing with a newer Python in /usr/local, as it uses the
new Python in /usr/local as C-API but links against the old
Python shipped by Apple in
/System/Library/Frameworks/Python.framework/Versions/2.3
Then I made my usual build with --disable-darwin and called
./src/vim
meaning vim in the build directory. And! everything worked.
Still, after make install, vim in /usr/local/bin showed the same
errors.
snip
Apparently make install strips something from the executable.
Solved/worked around by, eg:
--- a/src/Makefile Tue Mar 27 12:08:55 2007 +0200
+++ b/src/Makefile Tue Mar 27 12:52:35 2007 +0200
@@ -998,7 +998,7 @@ INSTALL_DATA_R = cp -r
INSTALL_DATA_R = cp -r
### Program to run on installed binary
-#STRIP = strip
+STRIP = strip -x
### Permissions for binaries {{{1
BINMOD = 755
--
Vim plugin to paste current GNU Screen buffer in (almost) any mode:
http://www.vim.org/scripts/script.php?script_id=1512
python omnicompletion with Python 2.5
Hello, I wanted to try out omnicompletion with Python 2.5, and I get the following: Error detected while processing function SNR62_DefPython: line 517: Traceback (most recent call last): Error detected while processing function SNR62_DefPython: line 517: File string, line 1, in module Error detected while processing function SNR62_DefPython: line 517: ImportError: dlcompat: dyld: vim Undefined symbols: Error detected while processing function SNR62_DefPython: line 517: /usr/local/lib/python2.5/lib-dynload/cStringIO.so undefined reference to _PyArg_ParseTuple expected to be defined in a d ynamic image Error detected while processing function SNR62_DefPython: line 517: /usr/local/lib/python2.5/lib-dynload/cStringIO.so undefined reference to _PyAr Error detected while processing function pythoncomplete#Complete: line 35: Traceback (most recent call last): Error detected while processing function pythoncomplete#Complete: line 35: File string, line 1, in module Error detected while processing function pythoncomplete#Complete: line 35: NameError: name 'vimcomplete' is not defined Error detected while processing function pythoncomplete#Complete: line 36: E121: Undefined variable: g:pythoncomplete_completions Error detected while processing function pythoncomplete#Complete: line 36: E15: Invalid expression: g:pythoncomplete_completions Anybody any idea where the problem is? Python installation (seems to work fine otherwise)? $ vim --version VIM - Vi IMproved 7.0 (2006 May 7, compiled Mar 25 2007 18:58:04) Included patches: 1-220 Compiled by [EMAIL PROTECTED] Huge version without GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() -gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra -perl +postscript +printer +profile +python +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: $VIM/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /usr/local/share/vim Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O3 -I/sw/include -arch ppc -g -O3 -I/sw/include -I/usr/local/include/python2.5 Linking: gcc -L/sw/lib -arch ppc -L/usr/local/lib -o vim -lncurses -liconv-L/usr/local/lib/python2.5/config -lpython2.5 -L/sw/lib/system-openssl/lib -lssl -lcrypto -lcurses -lpanel -lncurses -u _PyMac_Error $ uname -a Darwin krille.blacktrash.org 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc Thanks in advance for any pointers. c -- Vim plugin to paste current GNU Screen buffer in (almost) any mode: http://www.vim.org/scripts/script.php?script_id=1512
Re: python omnicompletion with Python 2.5
* Aaron Griffin on Monday, March 26, 2007 at 10:39:24 -0500: On 3/26/07, Christian Ebert [EMAIL PROTECTED] wrote: I wanted to try out omnicompletion with Python 2.5, and I get the following: Error detected while processing function Try the following in vim: :python import sys; print sys.version 2.5 (r25:51908, Dec 15 2006, 13:53:51) [GCC 3.3 20030304 (Apple Computer, Inc. build 1671)] c -- Vim plugin to paste current GNU Screen buffer in (almost) any mode: http://www.vim.org/scripts/script.php?script_id=1512
Re: python omnicompletion with Python 2.5
* Aaron Griffin on Monday, March 26, 2007 at 13:54:19 -0500: Hmmm, well, I don't really know what to say w.r.t. all that. The best I can do is push a new pythoncomplete out that isn't dependent on cStringIO. I think it may have been a pre-optimization anyway. But cStringIO is faster ;) I'll make a note of it and see what happens tonight. Might be good to check with someone who runs a normal Vim on Mac -- I only have console and compiled with --disable-darwin to work around case-insensitive file system; might be that this switch also breaks _complete_ python support. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: python omnicompletion with Python 2.5
Hi Aaron, * Aaron Griffin on Monday, March 26, 2007 at 13:54:19 -0500: Hmmm, well, I don't really know what to say w.r.t. all that. The best I can do is push a new pythoncomplete out that isn't dependent on cStringIO. I think it may have been a pre-optimization anyway. I'll make a note of it and see what happens tonight. I did a few experiments. As I compile with --disable-darwin, I build a Vim.app (that's how it's called on the Mac) for testing, and there things get even more confusing with a newer Python in /usr/local, as it uses the new Python in /usr/local as C-API but links against the old Python shipped by Apple in /System/Library/Frameworks/Python.framework/Versions/2.3 Then I made my usual build with --disable-darwin and called ./src/vim meaning vim in the build directory. And! everything worked. Still, after make install, vim in /usr/local/bin showed the same errors. Then I ran $ diff src/vim /usr/local/bin/vim and they differed. Then I *copied* src/vim to /usr/local/bin/vim and now omnicompletion, and of course :py import cStringIO, works! Very strange. Apparently make install strips something from the executable. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: case-sens in completion on Mac OS X
* A.J.Mechelynck on Sunday, March 25, 2007 at 11:07:35 +0200: Ricardo SIGNES wrote: I am running Vim 7.0.218, the latest build from macvim.org. I run the vim binary from inside the app bundle at the console to get my terminal vim. My filesystem is case-sensitive HFS+, but vim's filename completion acts case-insensitive. This is driving me CRAZY. If I have lib and LICENSE in a directory, and I hit lTab I expect lib to be completed, but instead it wants me to choose between the two. How can I fix this? Does it change if you use :set noignorecase (without the quotes)? In case this doesn't work and you only want console vim, you can could compile vim yourself with the following configure parameters (among others of your choice): ./configure --without-x --disable-gui \ --disable-gtk-check --disable-gtk2-check \ --disable-motif-check --disable-athena-check \ --disable-nextaw-check --disable-carbon-check \ --disable-darwin --with-mac-arch=current This works for me even on case insensitive HFS+. I don't know whether this would apply to a GUI version as well, though. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: buffer ring behaviour - how do I make it an MRU ring?
* Keith Hanlan on Friday, March 09, 2007 at 12:48:49 -0500: I want :bprev to take me to the most-recently-used buffer but I can't see a way to do that. It always follows the order in which the buffers where loaded. I use :bnext and :bprev (mapped to cntl-- and cntl--) to cycle through my buffer ring. However, it always cycles the same way; I would like :bprev to take me to the last buffer that I was using. It not (exactly) what you're after, and it's a different concept, but have tried what you can do with Ctrl-^ ? :help alternate-file :help Ctrl-^ :help :_# Sorry, if you've been there already. c -- Vim plugin to paste current GNU Screen buffer in (almost) any mode: http://www.vim.org/scripts/script.php?script_id=1512
Re: How do I make the current working directory follow the active document in Gvim?
* cga2000 on Monday, February 26, 2007 at 11:57:39 -0500: On Sun, Feb 25, 2007 at 07:57:39PM EST, A.J.Mechelynck wrote: - To change (once) to the dir of the current file :cd %:p:h Nice. But I'm not going to remember it until I understand it. I scoured the :help files but couldn't find and explanation of the syntax. :p is short for :print and :h is help. :help ::p :help ::h :help filename-modfiers You can find out eg. by :h :p and then pressing Ctrl-D, or tab. c -- Vim plugin to paste current GNU Screen buffer in (almost) any mode: http://www.vim.org/scripts/script.php?script_id=1512
Re: Marking an undo-block before ^U in insert-mode
* Tim Chase on Tuesday, February 20, 2007 at 09:13:17 -0600: I'm still not 100% sure why I got this craziness: inoremap c-u c-onopc-u This gives me a crazy E486: Pattern not found: insert which, I haven't searched for the word insert so this one makes me scratch my head. Bug perhaps? Vim-internals showing through? to try and reproduce something similar, I did vim -u NONE :set nocp :inoremap c-u c-oNopc-u inserted some text and hit control+U. This time I got E35: No previous regular expression. I suspect that the Nop isn't getting interpreted as the do nothing operator as described at :help nop but rather is being interpreted as less-than, en, oh, pee, greater-than and the en portion of it is trying to look for the last regexp. Try (untested): :inoremap c-u c-oltNopc-u See: :help c -- Vim plugin to paste current GNU Screen buffer in (almost) any mode: http://www.vim.org/scripts/script.php?script_id=1512
Re: Tutorial on mapping keys in Vim
Hi Yegappan, * Yegappan Lakshmanan on Wednesday, November 29, 2006 at 22:22:28 -0800: I have created a tutorial on mapping keys in Vim. http://www.geocities.com/yegappan/vim_maps_tutorial.txt This tutorial describes mode specific maps, key notations, tips about maps in various modes, etc. Let me know if you have any comments Unfortunately only a very short one: I like it, it's very useful, thank you very much! or suggestions on improving this tutorial. Not on this one (yet). But a similar thing on how to handle the 'tabstop', 'softtabstop', 'shiftwidth', 'expandtab' etc. options would be nice to have ;) Thanks again. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Execute command for current block of code
* Kevin Old on Wednesday, November 22, 2006 at 12:57:27 -0500: Actually, I didn't know that highlighting visually and hitting the : will give me the range. That's half the battle for me on this. I've tried putting that into a mapping like this: map vti :',' !perltidy vmap vti :!perltidyCR c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: generate a directory listing file with vim.
* A.J.Mechelynck on Monday, November 06, 2006 at 09:44:05 +0100: Method II : Using netrw - new . I just realize that this doesn't work for me (anymore) with latest Vim7 (it still works with Vim6.2 that I have here as well. It works neither works with netrw from CVS nor with the one I get with GetLatestVimScripts. Any idea what's going on? c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: generate a directory listing file with vim.
* Gary Johnson on Wednesday, November 08, 2006 at 12:54:43 -0800: On 2006-11-08, Christian Ebert [EMAIL PROTECTED] wrote: * A.J.Mechelynck on Monday, November 06, 2006 at 09:44:05 +0100: Method II : Using netrw - new . I just realize that this doesn't work for me (anymore) with latest Vim7 (it still works with Vim6.2 that I have here as well. It works neither works with netrw from CVS nor with the one I get with GetLatestVimScripts. Any idea what's going on? If you have installed a private/local version of netrw under ~/.vim, you must disable the netrw files in the vim share directory. Either remove them all or rename them all, e.g. by adding a suffix .orig. Ah, ok, thanks, that does the trick. I know you don't have to do that for any other plugin, but you do for netrw. I don't know why. Hm. In a way the GetLatestVimScripts doesn't make sense for the netrw stuff, because it does not real AutoInstall. -- Or, it's for someone like me, who doesn't mind turning off the system-wide netrw ... c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Command line tab completion
* Benji Fisher on Thursday, November 02, 2006 at 09:21:36 -0500: $ vim -u NONE :set nocp wildmenu wildmode=longest:list :help termiTab :help preserTab :help preser :preserve 'preserveindent''nopreserveindent' :help preser I was hoping for termin in the first case and preserve in the second, but I was stuck with termi and preser. HTH --Benji Fisher P.S. Has there been a patch that affects this? I am still using vim 7.0.000 . VIM - Vi IMproved 7.0 (2006 May 7, compiled Nov 1 2006 21:35:34) Included patches: 1-158 Compiled by [EMAIL PROTECTED] Huge version without GUI. Features included (+) or not (-): [...] c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: --enable-pythoninterp gives unrecognized option `-pthread' on MacOS X
* Bram Moolenaar on Friday, September 22, 2006 at 14:24:09 +0200: The configure script has a specific check for not adding -pthread on Mac OS/X. It looks like you used the --disable-darwin argument or somehow disabled Darwin in another way. Please check src/auto/config.log. I just found out that the warning when compiling w/o GUI must have gone with one of the recent patches. Thank you. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: strange mapping in Latex Suite ?
* Matias Grana on Monday, October 09, 2006 at 10:04:42 -0300: So I have two questions here: why a map on M-i ends up on 'é' ? And what is a good way to change this mapping? I mean, a way which works after an eventual update of LatexSuite. http://vim-latex.sourceforge.net/index.php?subject=faqtitle=FAQ#faq-e-acute http://vim-latex.sourceforge.net/index.php?subject=faqtitle=FAQ#faq-euro-symbols c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Font rendering on Mac
* David Goodlad on Thursday, October 05, 2006 at 17:07:09 -0700: Well, it looks fine on my macbook pro, where anti-aliasing works. The real question becomes, why won't antialiasing work on my other mac? Have you checked the setting of System Preferences-Appearance-Turn off text smoothing for font sizes ... ? [this is on 10.3.9, but there must be something similar on 10.4] You probably have, but just in case, and because I tend to overlook such trivial stuff ;) c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Problem with accents
* Giovanni Funchal on Sunday, October 01, 2006 at 13:52:08 +0200: I've recently installed kubuntu linux over vmware, then I used the adept package manager to install the following packages (6.4-006) vim vim-gtk vim-gui-common vim-latexsuite vim-runtime I have a french keyboard, and accents works everywhere: terminal, openoffice, etc BUT when I try to edit a latex .tex file with gvim, I can't type accentuated letters like é and à http://vim-latex.sourceforge.net/index.php?subject=faqtitle=FAQ#faq-e-acute http://vim-latex.sourceforge.net/index.php?subject=faqtitle=FAQ#faq-euro-symbols c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Getting the output of some commands into a buffer
* Meino Christian Cramer on Wednesday, September 27, 2006 at 04:16:55 +0200: there are several commands like :map or :version which put a lot of valuable informations (at least for a newbie like me) into a temporary something (buffer seems the wrong nameing to me here). I would like to get the output of those commands into a real buffer and become non non-volatile text. In addition to Tony's answer have a look at the thread Piping messages from ex commands into a new tab from a few days ago; eg. Message-ID: [EMAIL PROTECTED]. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Piping messages from ex commands into a new tab
* Benji Fisher on Tuesday, September 26, 2006 at 09:53:32 -0400: fun! TabMessage(cmd) redir = message silent execute a:cmd redir END tab split put=message endfun In case one wishes to have /only/ the command output in the tab, and no delay by messages: function! TabMessage(cmd) redir = message silent execute a:cmd redir END tabnew silent put=message endfunction c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Plain TeX support ?
* Meino Christian Cramer on Saturday, September 23, 2006 at 06:54:29 +0200: Looking into :help \TeX\ does not that much information about the support of generating nice and find documents via plain TeX. Where can I get informations about what I can do/download/install/read to get a TeX-support a la AucTeX for Emacs ? Personally I only use LaTeX, but the following Vim-scripts might be worth looking into, even for plain TeX: LaTeX-Suite http://vim-latex.sf.net/ is the one I use. auctex.vim http://www.vim.org/scripts/script.php?script_id=162 a smaller one, based on the above. You might want to search for more at http://www.vim.org/search.php. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Making vim fast
* Eric Smith on Monday, September 25, 2006 at 23:11:47 +0200: I have a number of large files open and generally experience slow performance. Have you tried the LargeFile plugin? http://www.vim.org/scripts/script.php?script_id=1506 c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: latin1 words in an utf-8 file
Hi Yakov,
* Yakov Lerner on Saturday, September 23, 2006 at 21:01:30 +0300:
If you can do the following two steps, then
you'll achieve what you want to obtain:
1) write your own decoder/encoder
from/to your mixed utf-8+latin format (in perl, C or in whatever language)
that just reads stdin and writes to stdout
2) setup autocmds analogously to of :help hex-editing
Then it will work. But. The real prolem is how the decoder
would know which bytes are latin1 vs which bytes are utf-8.
The same problem the encoder will have. You can solve it if you
define 2 special quoting chars as markup chars that delimit
latin1 parts.
For simple stuff \caps{latin1} would suffice. But in the real
virtual world it's easier to read from differently encoded files
by LaTeX' \input{latin1-file}.
Looking for special quoting chars, encoder and decoder
can do their work. Without quoting chars markup, it is
impossible. Ok ?
Ok ;) See also my reply to Tony.
Yakov set ignorecase Lerner
Thanks.
dirty note c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: latin1 words in an utf-8 file
Hi Tony,
* A.J.Mechelynck on Saturday, September 23, 2006 at 17:35:25 +0200:
Christian Ebert wrote:
* A.J.Mechelynck on Saturday, September 23, 2006 at 09:57:40 +0200:
#1.
cat file1.utf8.txt file2.latin1.txt file3.utf8.txt file99.utf8.txt
will produce invalid output unless the Latin1 input file is actually
7-bit US-ASCII. This is not a limitation of the cat program (which
inherently never translates anything) but a false manoeuver on the part
of the user.
Hm, I want illegal stuff, hehe.
Then don't use UTF-8 files.
Yup. Basically I can't edit files with mixed encodings. What
fooled me was that if I do in an utf-8 environment:
$ echo 'Vögel' file-utf8.txt
and then illegally:
$ echo 'Vögel' | iconv -f utf-8 -t iso-8859-1 file-utf8.txt
$ vim file-utf8.txt
Vim then decides to convert to latin1 automatically for
representation:
#v+
Vögel
Vögel
#v-
Makes sense as Vim considers 'ö' as legal latin1 chars. And
apparently there is no way to force Vim in a less sensible way ;)
like to represent the illegal chars with a placeholder.
Blinded by my (dirty workaround) purpose I hoped for a way to
force Vim /not/ to convert.
#2.
gvim
:if tenc == | let tenc = enc | endif
:set enc=utf-8 fencs=utf-bom,utf-8,latin1
ucs-bom
:e ++enc=utf-8 file1.utf8.txt
:$r ++enc=latin1 file2.latin1.txt
:$r ++enc=utf-8 file3.utf-8.txt
:saveas file99.utf8.txt
Then file99.utf8.txt is the same as the one produced with the
cat command. Which is actually what I want.
No. It is what the one produced with the cat command should have been, with
the Latin1 accented characters properly converted to UTF-8.
You are right, of course.
To summarize:
I tried to work around a shortcoming in a LaTeX package (it can't
parse utf input).
For my purposes the easiest workaround would have been the
dirtiest:
[LaTeX pseudo-code]
#v+
\usepackage[utf8]{inputenc}
\usepackage{soul}% - the package in question
Loads of legal utf-8 text ...
\begingroup\inputencoding{latin1}
\caps{short text in illegal iso-8859-1}
\endgroup
Loads of legal utf-8 text ...
#v-
This does not work in one file if I want to continue to edit the
loads of legal utf-8 text in Vim.
In the above simple case I could do:
$ voeg=`echo 'Vögel' | iconv -f utf-8 -t iso-8859-1`; \
sed -i~ -e s/\\caps{.*}/\\caps{$voeg}/ file-utf8.tex
to get the result (LaTeX output) I wanted.
Or I could write the group around \caps in a latin1 file and
\input it, or decide to switch to a latin1 environment ...
... or rewrite the LaTeX-package to accept utf-8 encoding --
which would be the cleanest solution, but unfortunately over my
head ATM.
So, what I had in mind was too dirty (for Vim).
Thanks for taking your time, Tony.
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: latin1 words in an utf-8 file
Hi Tony,
* A.J.Mechelynck on Saturday, September 23, 2006 at 09:57:40 +0200:
Christian Ebert wrote:
Is it possible to have eg. iso-8859-1 encoded words/passages in
an otherwise utf-8 encoded file? I mean, w/o automatic
without
conversion, and I don't need the iso passages displayed in a
readable way, but so I can still write the file in utf-8 w/o
changing the invalid iso-8859-1 chars?
Hm, hope I made myself clear.
Hm, I probably didn't.
snip detailed explanation with bleeding heart ;)
Corollary of the conclusion:
#1.
cat file1.utf8.txt file2.latin1.txt file3.utf8.txt file99.utf8.txt
will produce invalid output unless the Latin1 input file is actually 7-bit
US-ASCII. This is not a limitation of the cat program (which inherently
never translates anything) but a false manoeuver on the part of the user.
Hm, I want illegal stuff, hehe.
#2.
gvim
:if tenc == | let tenc = enc | endif
:set enc=utf-8 fencs=utf-bom,utf-8,latin1
ucs-bom
:e ++enc=utf-8 file1.utf8.txt
:$r ++enc=latin1 file2.latin1.txt
:$r ++enc=utf-8 file3.utf-8.txt
:saveas file99.utf8.txt
Then file99.utf8.txt is the same as the one produced with the
cat command. Which is actually what I want.
*But*:
Vim insists on converting the displayed text to latin1. What I
want is to have the contents displayed in utf-8 with a few
illegal characters in latin1.
Now I get:
#v+
Vögel - utf-8
Vögel - latin1
#v-
because Vim automatically converts to latin1. Whereas I'd like to
have it the other way round: with Vögel displayed as garbage,
but I can continue editing the file in _utf-8_.
Is this possible in *G*vim? (I don't have the GUI installed)
Example snippet from a fictitious LaTeX-file to show the purpose
(or to increase confusion):
#v+
The main part of the file is in utf-8 encoding and contains
non-ascii characters.
Then, I want to typeset, say, one word in \emph{spaced} small
caps. The \LaTeX-package that does this, is not capable to parse
utf-8 input, so this single word has to be in latin1 in case it
contains non-ascii chars:
\begingroup\inputencoding{latin1}
\caps{V?gel}
\endgroup
to use the above example (with ``?'' for garbage).
\caps{V\ogel} gives orthographically correct output but I lose
the kerning of the font.
The above example \emph{works,} but the main part of the file is
displayed in ``disected'' utf-chars.
Is it possible to have this the other way round without automatic
conversion to latin1?
#v-
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
--enable-pythoninterp gives unrecognized option `-pthread' on MacOS X
Hello, I wanted to ask this for quite a long time (Vim 6.4 actually): When I compile with --enable-pythoninterp I get the following warnings: $ head -n5 vim-make.log Starting make in the src directory. If there are problems, cd to the src directory and run make there cd src gnumake first CC=gcc -Iproto -DHAVE_CONFIG_H -I/sw/include-I/sw/include -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -I/usr/local/include -I/sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level/CORE -I/sw/include/python2.4 -pthreadsrcdir=. sh ./osdef.sh gcc: unrecognized option `-pthread' [...] etc. $ grep pthread vim-configure.log checking if -pthread should be used... yes checking for pthread_np.h... no $ ls -1 /usr/include/pthread* /usr/include/pthread.h /usr/include/pthread_impl.h $ vim --version VIM - Vi IMproved 7.0 (2006 May 7, compiled Sep 16 2006 00:05:46) Included patches: 1-109 Compiled by [EMAIL PROTECTED] Huge version without GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() -gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile +python +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: $VIM/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /usr/local/share/vim Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/sw/include -I/sw/include -I/sw/include -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -I/usr/local/include -I/sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level/CORE -I/sw/include/python2.4 -pthread Linking: gcc -L/sw/lib -L/usr/local/lib -o vim -lncurses -liconv -L/sw/lib -L/usr/local/lib /sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level/auto/DynaLoader/DynaLoader.a -L/sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level/CORE -lperl -lm -lc -L/sw/lib/python2.4/config -lpython2.4 -u _PyMac_Error This is on MacOS 10.3.9: $ uname -a Darwin krille.blacktrash.org 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc However it seems to work. But I can't be sure because I don't use 'pythoninterp' very often. Ideas anyone? c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: --enable-pythoninterp gives unrecognized option `-pthread' on MacOS X
* Benji Fisher on Friday, September 22, 2006 at 08:19:12 -0400: On Fri, Sep 22, 2006 at 09:53:06AM +0200, Christian Ebert wrote: Linking: gcc -L/sw/lib -L/usr/local/lib -o vim -lncurses -liconv -L/sw/lib -L/usr/local/lib /sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level/auto/DynaLoader/DynaLoader.a -L/sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level/CORE -lperl -lm -lc -L/sw/lib/python2.4/config -lpython2.4 -u _PyMac_Error As I mentioned in my reply to Bram I compile with --disable-darwin, otherwise the respective perl and python libs in /sw are not linked. Plus I like that Vim stays case sensitive regarding paths. I also have OS X 10.3.9, but I usually compile with the Carbon/Aqua GUI. I do not see pthread anywhere in the output of make. My bad. I don't want the GUI, and disabled Darwin. Where do your log files come from? ./configure 21 | tee vim-config.log Oops, just detected the nice log in src/auto; sorry. Are you using a script to compile vim? No. If you tell me what you do to configure and build, I can try to reproduce the problem. CFLAGS=-I/sw/include LDFLAGS=-L/sw/lib \ ./configure --prefix=/usr/local --with-features=huge \ --enable-multibyte --enable-pythoninterp --enable-perlinterp \ --without-x --disable-gui \ --disable-gtk-check --disable-gtk2-check \ --disable-motif-check --disable-athena-check \ --disable-nextaw-check --disable-carbon-check \ --disable-darwin --disable-nls \ --with-compiledby=[EMAIL PROTECTED] As in my other mail: If the warning is just a warning and nothing else, I can live with it. Thank you. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: --enable-pythoninterp gives unrecognized option `-pthread' on MacOS X
* Bram Moolenaar on Friday, September 22, 2006 at 14:24:09 +0200: The configure script has a specific check for not adding -pthread on Mac OS/X. It looks like you used the --disable-darwin argument Yes: ./configure --prefix=/usr/local --with-features=huge \ --enable-multibyte --enable-pythoninterp --enable-perlinterp \ --without-x --disable-gui \ --disable-gtk-check --disable-gtk2-check \ --disable-motif-check --disable-athena-check \ --disable-nextaw-check --disable-carbon-check \ --disable-darwin --disable-nls \ --with-compiledby=[EMAIL PROTECTED] This is a) because I like eg. tab path-completion stay case-sensitive even with the HFS+. b) I want Vim to use python 2.4 which is installed under /sw -- this works when I pass LDFLAGS=-L/sw/lib and CFLAGS=-I/sw/include to configure /only/ when I --disable-darwin; otherwise configure insists on eg. /Library/Python/2.3 If the warning is only a warning w/o further consequences I can live with it. But I wanted to ask to make sure. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Search messages (was: What is the information in the leftmost two columns and how do I turn it off?)
Hi Tony, * A.J.Mechelynck on Saturday, August 05, 2006 at 01:25:22 +0200: Christian Ebert wrote: * A.J.Mechelynck on Friday, August 04, 2006 at 19:51:53 +0200: You may want to determine which script or plugin is responsible: search for the word sign (i.e. the pattern /\sign\/ ) in the scripts listed in the output of the :scriptnames command. How exactly do you search the output of :scriptnames? You may write it to a file or a register (see :help :redir) This was the answer I was expecting, but you wrote a whole manual! Thank you very much; this is really kind. For the impatient I have a little oneliner: :new | redi @ | sil scrip | pu! | 0 d that opens a new window with the output of :scriptnames [ hm, one could make a nice function and command by extending that ] - look what Vim answers when you say :scriptnames - if some script seems particularly suspect, load it, e.g. and then you can go to a suspicious file under the cursor with Ctrl-W_Ctrl-F Thanks again. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
augroup! not working for VimLeave
Hello,
Consider the following:
augroup TestLeave
au!
au VimLeave * echo hello
augroup END
Now if I do:
:augroup! TestLeave
TestLeave is still echoing hello.
Whereas if I do:
:au! TestLeave
TestLeave is deleted.
Is this a case covered by:
*:augroup-delete* *E367*
:aug[roup]! {name} Delete the autocmd group {name}. Don't use
this if there is still an autocommand using
this group! This is not checked.
Or doesn't it make sense to put an au VimLeave in an augroup
anyway?
Would be nice if someone could elaborate a bit on this.
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: augroup! not working for VimLeave
* Gary Johnson on Monday, July 31, 2006 at 01:13:10 -0700:
To paraphrase Will Rogers: All I know is what I read in the
manual.
heh
:help :autocmd-remove says,
:au[tocmd]! [group] Remove ALL autocommands.
And as you discovered, :help augroup-delete says not to execute
:aug[roup]! {name}
if the group still contains an autocommand. So to do what you want
to do, you should use :au! TestLeave and not :aug! TestLeave.
Thanks Will^WGary.
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: AsNeeded?
* A.J.Mechelynck on Sunday, July 30, 2006 at 10:59:55 +0200: Looks like AsNeeded didn't find SIDTlist_Session_Load in taglist because taglist's script number had changed from 23 to something else, or because taglist wasn't reloaded (yet?). Try moving taglist out of AsNeeded's scope and having it load unconditionally. I don't know AsNeeded well enough to know if it's a bug or not. taglist uses au FuncUndefined as its own AsNeeded mechanism. This might collide with AsNeeded. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: please, comment my script
* Benji Fisher on Wednesday, July 26, 2006 at 22:58:07 -0400: On Tue, Jul 25, 2006 at 12:36:44AM +0400, Pavel Volkovitskiy wrote: map C-S :call PySort()CR How about calling it directly from Visual mode? :vmap C-S :C-U PySort()CR For the above: Would :vmap C-S Esc:PySort()CR do the same thing? If no, what is the difference? If yes, what is the canonical way to do it? TIA c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
C-U or Esc in :vmap (was: please, comment my script)
* Benji Fisher on Thursday, July 27, 2006 at 13:13:39 -0400:
On Thu, Jul 27, 2006 at 09:34:59AM +0200, Christian Ebert wrote:
* Benji Fisher on Wednesday, July 26, 2006 at 22:58:07 -0400:
:vmap C-S :C-U PySort()CR
For the above: Would
:vmap C-S Esc:PySort()CR
do the same thing?
If no, what is the difference?
If yes, what is the canonical way to do it?
Since we are both using :vmap and not :vnoremap, we are both
vulnerable to unexpected results from user-defined mappings.
Yes, I actually use :vnoremap, but concentrated on C-U vs.
Esc.
If the user has 'insertmode' set, then Esc will go to Insert mode
rather than Normal mode, You can use C-\C-N to be safe.
Ah, didn't think of that ... but :help 'insertmode' says:
However, when Esc is used inside a mapping, it behaves like
'insertmode' was not set. This was done to be able to use the same
mappings with 'insertmode' set or not set.
Interesting though, :help c_Ctrl-\ takes me to c_Ctrl-\_e ...
Your version can be abbreviated, if you keep your :map , to
:vmap script C-S C-\C-NC-S
Hm. Now I have to try to understand what exactly C-\C-N does
...
Check the docs before relying on this, but IIRC :vmap and :vnoremap
behave the same if you add script .
Indeed.
:help :map-script
Note: :map script and :noremap script do the same thing. The
script overrules the command name. Using :noremap script is
preferred, because it's clearer that remapping is (mostly) disabled.
The mapping I had in mind goes in fact like so:
:vnoremap script PlugMyscriptDo Esc:call MyscriptDo()CR
I just wanted to know, whether :C-Ucall MyscriptDo()CR as
{rhs} is preferred, faster, or has other advantages.
Other than these minor differences, my original suggestion and
yours should do exactly the same things.
Ok. Thanks.
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Other European languages on a US keyboard
* A.J.Mechelynck on Saturday, July 22, 2006 at 22:40:45 +0200:
The French oe (o, e-dans-l'o) is not defined in the Latin1 encoding,
neither in capitals (as for titles or if the word oeuf [egg] is the
first of a sentence), nor in lowercase. You need UTF-8 for it,
No. Just latin9 or ISO8859-15 (Look at the header of this mail).
Mon cœur.
This is on a Mac with a German keyboard, but using actually an
American keyboard layout. I enter the œ with Alt-q (the Alt
key on Mac keyboard corresponds to the Modifier key on other
keyboards I believe).
$ echo $LANG
en_US.ISO8859-15
Alain Bench @ mutt-users pointed me to this site:
http://www.in-ulm.de/~mascheck/locale/
where you can get also a little utility at
http://www.in-ulm.de/~mascheck/locale/checklocale.c
It gives the following output here:
[Latin1/9] If there's no real copyrightsymbol at the end of this sentence,
then your terminal/terminalemulator/font is not ISO8859-1/15 ready: ©
- Current environment settings:
LANG= en_US.ISO8859-15
- Implicitly setting all locale categories with LANG succeeded.
Testing LC_CTYPE with isprint():
# # # # # # # # # # # # # # # #
# # # # # # # # # # # # # # # #
! # $ % ' ( ) * + , - . /
0 1 2 3 4 5 6 7 8 9 : ; = ?
@ A B C D E F G H I J K L M N O
P Q R S T U V W X Y Z [ \ ] ^ _
` a b c d e f g h i j k l m n o
p q r s t u v w x y z { | } ~ #
# # # # # # # # # # # # # # # #
# # # # # # # # # # # # # # # #
¡ ¢ £ € ¥ Š § š © ª « ¬ ® ¯
° ± ² ³ Ž µ ¶ · ž ¹ º » Œ œ Ÿ ¿
À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï
Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß
à á â ã ä å æ ç è é ê ë ì í î ï
ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ
- Testing LC_MESSAGES with perror(), but it's a libc message.
- Implicitly setting LC_CTYPE by LANG succeeded.
- Implicitly setting LC_NUMERIC by LANG succeeded.
- Implicitly setting LC_TIME by LANG succeeded.
- Implicitly setting LC_COLLATE by LANG succeeded.
- Implicitly setting LC_MONETARY by LANG succeeded.
- Implicitly setting LC_MESSAGES by LANG succeeded.
Mind you, what you will actually see might depend eventual broken
mailer settings, missing characters in fonts etc.
But I can write cedille, ae, oe, a-ring, several vowels with
trema and even € EURO.
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: line wrap question
* K.S.Sreeram on Monday, July 03, 2006 at 22:57:08 +0530: In 'set wrap' mode, say I have a single long line which wraps and forms 5 screen lines. Now when I press 'j', the cursor jumps over the 5 lines and goes to the next physical line(6th screen line). Is it possible for me to configure vim, so that cursor movement keys go to the next screen line, instead of the next physical line? :help gj c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: regexp select and place elsewhere
* Jerin Joy on Thursday, June 29, 2006 at 14:28:51 +0530:
I have data that looks like this
input [4:0] a.b.c.d;
which I need to replace with
input a.b.c.d [4:0] d;
ie. I want to copy a.b.c.d and place it after input and replace it
with d after [4:0].
:s/\(\[[^]]\+\]\) \(\([a-z]\.\)\{3}\([a-z]\)\);/\2 \1 \4;/
does it for your example, but I don't know which other
requirements and/or restrictions you have.
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Bug with gU and German sharp s?
* Bram Moolenaar on Friday, June 16, 2006 at 17:24:20 +0200: I'll leave it up to language specialists to decide whether making straße uppercase should result in STRAßE or STRASSE. I thought it was STRASSE. Historic: STRASZE Now: STRASSE See: http://de.wikipedia.org/wiki/Versal-Eszett Logically it's much easier to use STRAßE, because the length doesn't change and the reverse operation works. STRASSE made lower case is strasse... The Swiss are more logic (they write Strasse) but also more prone to confusion: Ich trinke Alkohol in Massen. -- which might mean I drink alcohol in moderation or I drink alcohol galore. c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
failure to create de .spl files via aap
Hello, Following the README's suggestion not to bother with creating .spl files by hand (which I did some time ago eg. with de.latin1.spl) I tried to go the easier way via aap in vim7.e07. Creating the french fr.latin1.spl, fr.latin1.sug, fr.utf-8.spl, fr.utf-8.sug works fine. When I try de, first the patching fails. So I changed de_20.diff and de_DE.diff like so: --- de_20.diff.orig 2006-04-24 17:07:56.0 +0200 +++ de_20.diff 2006-04-24 17:08:13.0 +0200 @@ -523,11 +523,3 @@ + SAL ZURÜCK^^ ZURIK + SAL ZUVER^^ ZUFA# x + SAL ZZ -*** de_20.orig.dic Sat Nov 26 19:59:53 2005 de_20.dic Mon Jan 2 20:19:18 2006 -*** -*** 1,3 - 314626 -- 23394 - A-Bombe/N 1,2 --- de_DE.diff.orig 2006-04-24 17:01:35.0 +0200 +++ de_DE.diff 2006-04-24 17:02:40.0 +0200 @@ -523,11 +523,3 @@ + SAL ZURÜCK^^ ZURIK + SAL ZUVER^^ ZUFA# x + SAL ZZ -*** de_DE.orig.dic Sat Nov 26 19:59:52 2005 de_DE.dic Mon Jan 2 15:35:27 2006 -*** -*** 1,3 - 319017 -- 23508 - A-Bombe/N 1,2 Maybe I would get the same by running app -k but either way I get BUS errors in the end: $ tail /usr/local/src/vim7/runtime/spell/de/AAPDIR/log Compressed 684 of 96861 nodes; 96177 (99%) remaining Writing spell file ../de.latin1.spl ... Done! Estimated runtime memory use: 9109400 bytes Reading back spell file... Performing soundfolding... [?1lVim: Caught deadly signal BUS Vim: Finished. [34;1H error: Error in recipe /usr/local/src/vim7/runtime/spell/de/main.aap line 36: Shell command returned 1 Apparently it chokes when trying to create the .sug file? On a first glance de.latin1.spl seems to work though. Anybody else experiencing this? Or knows what to do? TIA c -- _B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
