2007/5/15, Micah Cowan [EMAIL PROTECTED]:
Please note that he had already given you this exact same answer already
in his last message, including and especially the bit that \n is an
end-of-line (line terminator), not a open-new-line (line separator).
This is generally true for all operating
2007/5/15, Micah Cowan [EMAIL PROTECTED]:
Thomas Michael Engelke wrote:
But that's arguing semantics when the core of the problem is known
now. I apologize for having a different set of mind and not
understanding the problem instantly.
This is not a fair remark, considering I pointed out
2007/5/14, Andy Wokula [EMAIL PROTECTED]:
Thomas Michael Engelke schrieb:
:set fileformats?
gives
fileformats=dos,unix, so both formats are available, yet the
detection and switching does not seem to work.
Are you sure _every_ line ends in ^M?
Positive. Every single line shows an ^M
2007/5/15, A.J.Mechelynck [EMAIL PROTECTED]:
Thomas Michael Engelke wrote:
2007/5/14, Andy Wokula [EMAIL PROTECTED]:
Thomas Michael Engelke schrieb:
:set fileformats?
gives
fileformats=dos,unix, so both formats are available, yet the
detection and switching does not seem to work
2007/5/15, A.J.Mechelynck [EMAIL PROTECTED]:
Thomas Michael Engelke wrote:
2007/5/15, A.J.Mechelynck [EMAIL PROTECTED]:
Thomas Michael Engelke wrote:
2007/5/14, Andy Wokula [EMAIL PROTECTED]:
Thomas Michael Engelke schrieb:
:set fileformats?
gives
fileformats=dos,unix, so
Hello!
I just opened one of the files we develop, written by another
programmer. I can see a ^M at the end of every line.
I quickly check the mailing list archive and find out, that this
mainly depends on the setting of fileformat. I check fileformat
and find out that it's unix. Ah, the
:set fileformats?
gives
fileformats=dos,unix, so both formats are available, yet the
detection and switching does not seem to work.
2007/5/14, Yongwei Wu [EMAIL PROTECTED]:
Hi Thomas,
On 14/05/07, Thomas Michael Engelke [EMAIL PROTECTED] wrote:
Hello!
I just opened one of the files we
I'm using vim7 from my Total Commander under Windows XP with the
following command line:
vim70\gvim.exe --remote-tab-silent filename
Whenever I try to open a file from a UNC path (e.g.
\\Cd-server\HKR_304B\install.inf ), I get the attached message,
roughly translated as
Directory
Hello!
I am using the following mapping:
map F4 [I:let nr = input(Match: )Barexe normal . nr .[\tCR
This displays a list of all lines with occurances of the word under
the cursor on it, assigns an incremental number to it and lets me pick
one to jump to. This works fine.
But I know that vim7
2007/2/6, Vigil [EMAIL PROTECTED]:
Hopefully this will be available on google videos.
Yes, as a german it's an awfully long way just to meet Bram once. I
hope to see this lecture pop up as a Torrent or or Goggle Video.
2007/2/8, Marc Weber [EMAIL PROTECTED]:
On Thu, Feb 08, 2007 at 01:30:37PM +0100, Thomas Michael Engelke wrote:
Can anybody give me a hint on how to rewrite the mapping so I get such
a conext menu instead of a numbered list?
Get the word under the cursor using expand('cword')
See completion
2007/2/8, Guillaume Bog [EMAIL PROTECTED]:
Hi everbody,
I'm new on this list. I use vim in a terminal on ubuntu everyday and
still need some help for efficient use. If the file i'm editing is
longer than one screen and I want to paste it somewhere else (say in a
firefox textarea), I have to go
Hello,
I'm trying to use a regex for searching in a file. I noticed that
inside square brackets \w seems to loose all magical matching
abilities. Is there a way to reverse that loss or do I have to specify
everything inside [] explicitly?
Regards,
Thomas Engelke
Berlin, Germany
--
GPG-Key:
2007/1/10, Jürgen Krämer [EMAIL PROTECTED]:
Hi,
Thomas Michael Engelke schrieb:
I have a problem with indendation of a piece of Progress code. It's
representative of a bit of indendation problems I have now and again,
always indenting way too far without any visible cause. I hope someone
Hello,
I'm using vim excessively for developing in Progress 4GL. Sometimes, I
stumble upon an odd behaviour and don't know if it's due to a setting
in the syntax file (progress.vim) or due to a problem in vim itself.
Finally, I have a reproducable for one of those oddities.
In the attached
Hello,
I have found an oddity in vim which I'm not sure is a bug and/or known.
I have yanked a visual block of some lines of code and try to put it
in somewhere else. There a strange effect happens: depending on if
there is either a character or a beginning of line left besides the
cursor,
2006/12/6, A.J.Mechelynck [EMAIL PROTECTED]:
Thomas Michael Engelke wrote:
Hello,
I have found an oddity in vim which I'm not sure is a bug and/or known.
I have yanked a visual block of some lines of code and try to put it
in somewhere else. There a strange effect happens: depending
Hello!
I am looking for a way to mimic a functionality I've seen in the
editor ED4Win (http://www.softasitgets.com/). What I want to do is to
automagically upcase every written word that is considered a keyword.
I program in Progress 4GL and use the syntax file from the gvim
standard
Hello!
I'm not sure if it was always the case or if this is a recent change
(through vim 7). I am not able to undo anything after saving a file.
Is this normal? What settings are involved? How can I change this
behaviour? The help-file for undo is pretty silent regarding this.
Regards,
Thomas
2006/6/30, Michael Naumann [EMAIL PROTECTED]:
Do you have
:set hidden
If not, you should.
HTH, Michael
On Friday 30 June 2006 11:59, Thomas Michael Engelke wrote:
Hello!
I'm not sure if it was always the case or if this is a recent change
(through vim 7). I am not able to undo anything
2006/4/9, linda. s [EMAIL PROTECTED]:
I read the help file of cw but really can not understand what it means.
I use / to get the word i want to replace, then no matter i type :cw
or cw, unexpected results show.
If you are standing on the word you want to change, just use cw to
change the word
21 matches
Mail list logo
