Hiding ^M

Hiding ^M

[Óscar Fuentes]

For buffers with certain major mode, I'll like to hide ^M characters. It
is not possible to remove them and adjusting the eol settings of the
buffer is not an option either (the lines that ends with ^M are mixed
with "normal" lines).

Setting the `escape-glyph' face to white foreground would do. Setting
the specific face of the ^M character would be okay too. But that should
only apply to buffers with an specific major mode.

Re: Hiding ^M

[Juanma Barranquero]

> For buffers with certain major mode, I'll like to hide ^M characters. It
> is not possible to remove them and adjusting the eol settings of the
> buffer is not an option either (the lines that ends with ^M are mixed
> with "normal" lines).
>
> Setting the `escape-glyph' face to white foreground would do. Setting
> the specific face of the ^M character would be okay too. But that should
> only apply to buffers with an specific major mode.

You can try this

(define-minor-mode hide-^M-mode
    "Minor mode to hide ^M."
  :init-value nil
  :lighter "hide^M"
  (setq buffer-display-table
        (and hide-^M-mode
             (or (get 'hide-^M-mode :table)
                 (let ((table (or (copy-sequence standard-display-table)
                                  (make-display-table))))
                   (aset table ?\^M [?\u00A0])
                   (aset table ?\^I (vector (make-glyph-code ?\^I 'underline)))
                   (put 'hide-^M-mode :table table))))

and then setting hide-^M-mode in the mode hooks.

    Juanma

Re: Hiding ^M

[Torsten Mueller]

Óscar Fuentes <ofv@wanadoo.es> schrieb:

> For buffers with certain major mode, I'll like to hide ^M
> characters. It is not possible to remove them and adjusting the eol
> settings of the buffer is not an option either (the lines that ends
> with ^M are mixed with "normal" lines).

Yes, if there're ^M visible at the end of lines this is a notification
that there's a mix. I would not make them invisible. I would really
prefer to remove them because this mix is a relict from using
different editors who left the file in an inconsistent state.

I use a small file called eol-conversion.el for removing. It allows to
specify what kind of line ending should be used now for all lines.

T.M.

Re: Hiding ^M

[Mike Treseler]

Óscar Fuentes wrote:
> For buffers with certain major mode, I'll like to hide ^M characters. It
> is not possible to remove them and adjusting the eol settings of the
> buffer is not an option either (the lines that ends with ^M are mixed
> with "normal" lines).

DOS files that have been edited by many people
often have mismatched carriage returns.
These files should be cleaned before being used for anything.

I just

M-x Query replace regexp: ^M
Query replace regexp ^M with:
<Enter>

and do a few manually,
then '!' for the rest.

Then
M-x buffer-to-dos

or

buffer-to-unix

And all is well.

 -- Mike Treseler



> 

Re: Hiding ^M

[Óscar Fuentes]

Torsten Mueller <dev-null@shared-files.de> writes:

> Óscar Fuentes <ofv@wanadoo.es> schrieb:
>
>> For buffers with certain major mode, I'll like to hide ^M
>> characters. It is not possible to remove them and adjusting the eol
>> settings of the buffer is not an option either (the lines that ends
>> with ^M are mixed with "normal" lines).
>
> Yes, if there're ^M visible at the end of lines this is a notification
> that there's a mix. I would not make them invisible. I would really
> prefer to remove them because this mix is a relict from using
> different editors who left the file in an inconsistent state.

I agree, but the advice does not apply here because that major mode
displays a series of diffs taken from all edited files on a git working
tree. Some have crlf line endings, and they are shown as ^M.

[snip]

Re: Hiding ^M

[Tim X]

Óscar Fuentes <ofv@wanadoo.es> writes:

> Torsten Mueller <dev-null@shared-files.de> writes:
>
>> Óscar Fuentes <ofv@wanadoo.es> schrieb:
>>
>>> For buffers with certain major mode, I'll like to hide ^M
>>> characters. It is not possible to remove them and adjusting the eol
>>> settings of the buffer is not an option either (the lines that ends
>>> with ^M are mixed with "normal" lines).
>>
>> Yes, if there're ^M visible at the end of lines this is a notification
>> that there's a mix. I would not make them invisible. I would really
>> prefer to remove them because this mix is a relict from using
>> different editors who left the file in an inconsistent state.
>
> I agree, but the advice does not apply here because that major mode
> displays a series of diffs taken from all edited files on a git working
> tree. Some have crlf line endings, and they are shown as ^M.
>

Doesn't GIT have some sort of setting to handle this?

In SVN you would set the eol-style property to something like 'native'.
Then, SVN would handle eol differences automatically and ensure such
differences were not considered in version diffs etc. This eliminates
spurious differences caused by editors on different platforms that use
different eol styles. 

Tim



>
>
>

-- 
tcross (at) rapttech dot com dot au

Re: Hiding ^M

[Óscar Fuentes]

Tim X <timx@nospam.dev.null> writes:

>> I agree, but the advice does not apply here because that major mode
>> displays a series of diffs taken from all edited files on a git working
>> tree. Some have crlf line endings, and they are shown as ^M.
>
> Doesn't GIT have some sort of setting to handle this?

It has settings for eol conversion. In this case, I don't want those
conversions to take effect, because those files are supposed to have
crlf line endings.

[snip]

Re: Hiding ^M

[Tim X]

Óscar Fuentes <ofv@wanadoo.es> writes:

> Tim X <timx@nospam.dev.null> writes:
>
>>> I agree, but the advice does not apply here because that major mode
>>> displays a series of diffs taken from all edited files on a git working
>>> tree. Some have crlf line endings, and they are shown as ^M.
>>
>> Doesn't GIT have some sort of setting to handle this?
>
> It has settings for eol conversion. In this case, I don't want those
> conversions to take effect, because those files are supposed to have
> crlf line endings.
>

Under SVN, if you set eol-style to native, the SVN client takes care of
all this conversion stuff - it does not get into the repository - more
specifically, differences in client eol requirements are handled at the
client level and therefore don't affect what is in the repository and at
the same time eliminate issues of different eol styles because of users
with different clients. I would expect GIT to have something similar. 

Tim
>
>
>

-- 
tcross (at) rapttech dot com dot au