Re: How to distinguish [L]esen ( Readonly) from (L)öschen (Delete) ?
Hi, Georg Dahn wrote: Hi! --- Andre Massing <[EMAIL PROTECTED]> wrote: probably a rather stupid question, but using german language makes it impossible for me to choose (L)öschen (Delete) instead of [L]esen (Readonly) by typing just "l" if there exists a swap-file from a chrashed session. This is an error of the german translation, which unfortunately has been noticed only after the release of Vim 7.0. Since I am the maintainer of the German translation for some months now, I am very sorry for this inconvenience. There is a newer file on the FTP server of Vim: http://ftp.vim.org/editors/vim/messages/de.po Just compile this and replace the distributed version with the compiled version of the latest messages. If you cannot compile it yourself, be free to ask me for my compiled version (I have compiled it under MS Windows, thus I am not sure, if it will work on Linux, too). I fetched the file and recompiled vim, it works pretty fine now (under Linux), so thanks a lot! Regards, Andre
How to distinguish [L]esen (Readonl y) from (L)öschen (Delete) ?
Original Message From: - Sun Jul 16 18:41:05 2006 X-Mozilla-Status: 0001 X-Mozilla-Status2: 0080 Message-ID: <[EMAIL PROTECTED]> Date: Sun, 16 Jul 2006 18:40:54 +0200 From: Andre Massing <[EMAIL PROTECTED]> User-Agent: Thunderbird 1.5.0.4 (X11/20060713) MIME-Version: 1.0 To: vim@vim.org Subject: How to distinguish [L]esen (Readonly) from (L)öschen (Delete) ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Dear Vimmers, probably a rather stupid question, but using german language makes it impossible for me to choose (L)öschen (Delete) instead of [L]esen (Readonly) by typing just "l" if there exists a swap-file from a chrashed session. So how can I tell vim to delete this file (in a console vim session)? Thanks in advance for any hints. Regards, Andre
Re: bug? abbreviate does not work properly gvim-70d02
Andre Massing schrieb: > Benji Fisher schrieb: > >>On Thu, Apr 13, 2006 at 02:50:28PM +0200, "André Massing" wrote: >> >> >>>Hi All, >>> >>>I defined an abbrevation :ab NK Newton-Kaskade , but to my surprise this >>>abbrevation is not expanded in Insert Mode after typing , (but was >>>expanded with or .) Actually it works properly only if I use iab >>>NK Newton-Kaskade. This phenomena only occurs when I use gvim7 but neither >>>in a terminal vim7 nor in any (gui or non-gui) prior version of vim (6.4.7). >>>Is this a bug in gvim7? >> >> >> I cannot confirm this. Did you check for conflicting abbreviations >>and trailing spaces in the :ab command? >> >>HTH --Benji Fisher >> >> > > > > Yes I did, there were no other abbrevations and no trailing spaces. Actually I > realizied that some problems occur with my settings if I load an old session > via source. Last time when I started with an old sessin, my textwidth were not > recognized and although set tw? showed me the assigned value, vim did not > break > any line automatically. But it broke lines with the gq command. Starting a new > gvim7, everything worked fine (tw, abbrevations and so on). > That seems rather strange to me. Any suggestions how I could investigate this > problem since this phenomena prevents me from using sessions and forces me to > remember and reopen all my files I had worked on (which is sometimes quite > hard > for me :-) ) > > Best wishes > Andre > Okay, now I realized that there is no connection with my sourced session but rather with some (LaTeX) files. So simply loading a (special) LaTeX File breaks some settings (both in vim and gvim, version 6 and 7). Andre
Re: bug? abbreviate does not work properly gvim-70d02
Benji Fisher schrieb: > On Thu, Apr 13, 2006 at 02:50:28PM +0200, "André Massing" wrote: > >>Hi All, >> >>I defined an abbrevation :ab NK Newton-Kaskade , but to my surprise this >>abbrevation is not expanded in Insert Mode after typing , (but was >>expanded with or .) Actually it works properly only if I use iab >>NK Newton-Kaskade. This phenomena only occurs when I use gvim7 but neither >>in a terminal vim7 nor in any (gui or non-gui) prior version of vim (6.4.7). >>Is this a bug in gvim7? > > > I cannot confirm this. Did you check for conflicting abbreviations > and trailing spaces in the :ab command? > > HTH --Benji Fisher > > Yes I did, there were no other abbrevations and no trailing spaces. Actually I realizied that some problems occur with my settings if I load an old session via source. Last time when I started with an old sessin, my textwidth were not recognized and although set tw? showed me the assigned value, vim did not break any line automatically. But it broke lines with the gq command. Starting a new gvim7, everything worked fine (tw, abbrevations and so on). That seems rather strange to me. Any suggestions how I could investigate this problem since this phenomena prevents me from using sessions and forces me to remember and reopen all my files I had worked on (which is sometimes quite hard for me :-) ) Best wishes Andre
