Thomas Michael Engelke wrote:
In the programming language I currently write, using the
seperator string somewhere in the string I'm parsing gives a
new entry. So a string containing only a line seperator
char/pattern would have 2 entries, which in this case would
mean 2 lines. As I see now, this
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 ou
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 sy
Gene Kwiecinski wrote:
"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 at the end. "set fileformat"
gives "unix" after loading. Setting fileformat to
Gene Kwiecinski wrote:
"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 at the end. "set fileformat"
>> gives "unix" after loading. Set
>Uhhh, don't think it *should* automagically delete the ^Ms. I'm always
>running into that, and in addition to an almost reflexive alt-EIFD to
go
>dos-mode, I *still* always have to ':s/^V^M' to get rid of 'em, and I'm
I sit corrected, so before anyone yells at me :D I should point out that
mos
>>>"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 at the end. "set fileformat"
>gives "unix" after loading. Setting fileformat to "dos" doesn't chan
Thomas Michael Engelke wrote:
> 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.
>>
>> Th
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 to you, privately,
that he made the statemen
* A.J.Mechelynck [2007.05.15 08:01]:
> If you had, as I already told you twice (this is
> the third one) done
>
> :set fileformats=
> :e ++ff=dos list02.p
> :w
>
> your file would have been repaired immediately.
> SO WHY DIDN'T YOU?
Or equivalently:
:e list02.p
GA " add ^M at
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/15, A.J.Mechelynck <[EMAIL PROTECTED]>:
>> >> Thomas Michael Engelke wrote:
>> >> > 2007/5/14, Andy Wokula <[EMAIL PROTECTED]>
Thomas Michael Engelke wrote:
Assuming that fileformat "unix" means 0x10 means "open a new
line" which seems to be the case (0x13 stays as ^M, 0x10 is
interpreted as a new line), shouldn't this mean that in the
last line there is a line break missing?
It's not important here, but for the record
Thomas Michael Engelke wrote:
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 filefor
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
>>
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 both formats are available, yet
Thomas Michael Engelke wrote:
> Hello Tony, and thanks for your extensive answer. Unfortunately, this
> is what I can report. To make things easier, I'll attach the file I am
> talking about to this message so that you can either check for
> yourselves and/or see that I'm telling the truth.
>
> Wh
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 switchin
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.
Are you sure _every_ line ends in "^M"?
P
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 show
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"?
--
Regards,
Andy
EOM
: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 file
Hi Thomas,
On 14/05/07, Thomas Michael Engelke <[EMAIL PROTECTED]> wrote:
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 o
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
23 matches
Mail list logo
