From: Dan McCarthy <daniel.c.mccarthy@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 66748@debbugs.gnu.org
Subject: bug#66748: 29.1; Remote files lose their coding system & line ending style
Date: Thu, 26 Oct 2023 08:08:36 -0400 [thread overview]
Message-ID: <CAAoRiOUPbCw94BmGPYWHb87mEYPrck5AWT6VkwWuwr5NKD=+_A@mail.gmail.com> (raw)
In-Reply-To: <87edhi8tz2.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Yes, that appears to be the same thing. Thanks for the pointer and sorry
for the duplicate.
Dan
On Wed, Oct 25, 2023 at 1:58 PM Michael Albinus <michael.albinus@gmx.de>
wrote:
> Dan McCarthy <daniel.c.mccarthy@gmail.com> writes:
>
> Hi Dan,
>
> > I visited a remote file with DOS line endings over SSH, added a line
> > and
> > saved. The file still has \r\n at every line, but now Emacs reports
> > "Unix-style LF" as the line-ending style; if I add more text and save
> > again, the line endings are converted to \n.
> >
> > Something similar happens with remote files in iso-latin-1. After
> > saving, they're converted to utf-8-unix. I noticed this in `git diff`:
> > it reported changes in some non-ASCII text that I hadn't touched,
> > which was surprising.
> >
> > Neither problem occurs with local files.
>
> This sounds like bug#65022. Please read the discussion at
> https://debbugs.gnu.org/65022, which contains also a patch which you
> might try. It will be fixed in the upcoming Emacs 29.2.
>
> Best regards, Michael.
>
[-- Attachment #2: Type: text/html, Size: 1629 bytes --]
next prev parent reply other threads:[~2023-10-26 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 15:52 bug#66748: 29.1; Remote files lose their coding system & line ending style Dan McCarthy
2023-10-25 17:58 ` Michael Albinus
2023-10-26 12:08 ` Dan McCarthy [this message]
2023-10-26 13:19 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAoRiOUPbCw94BmGPYWHb87mEYPrck5AWT6VkwWuwr5NKD=+_A@mail.gmail.com' \
--to=daniel.c.mccarthy@gmail.com \
--cc=66748@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.