From: Michael Albinus <michael.albinus@gmx.de>
To: yyoncho <yyoncho@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Tramp and conversion of \r\n into \n
Date: Thu, 10 Dec 2020 14:44:34 +0100 [thread overview]
Message-ID: <87r1nx93nh.fsf@gmx.de> (raw)
In-Reply-To: <CACCVLQUqhQ=OW5jCH+m9pQpR9D24aMfttuxwT1hsPWAoN0M3vA@mail.gmail.com> (yyoncho@gmail.com's message of "Wed, 9 Dec 2020 09:34:27 +0200")
yyoncho <yyoncho@gmail.com> writes:
> Hi Michael,
Hi Ivan,
> I am writing this regarding the following issue on lsp-mode's bug
> tracker: https://github.com/emacs-lsp/lsp-mode/issues/2375 . The issue
> is that \r\n are converted to \n but only when connecting to linux
> from mac.
>
> Using (set-process-coding-system result 'no-conversion 'no-conversion)
> and settinginhibit-eol-conversion to t does not work(or at least this
> is what was reported by the users).
>
> Can you suggest what the issue might be?
Hard to say (and I have no Mac for testing). Maybe you bring me in
contact with a user beaten by this, and I'll try to see with her, what
happens. That means reproduce the problem while there are Tramp traces,
and likely to repeat the tests several times, applying patches proposed
by me.
> Thanks,
> Ivan
Best regards, Michael.
next prev parent reply other threads:[~2020-12-10 13:44 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 7:34 Tramp and conversion of \r\n into \n yyoncho
2020-12-10 13:44 ` Michael Albinus [this message]
2020-12-11 14:11 ` yyoncho
-- strict thread matches above, loose matches on Subject: below --
2020-12-11 7:46 APEL Martin
2020-12-11 9:15 ` Michael Albinus
2020-12-11 9:59 ` APEL Martin
2020-12-11 10:26 ` Michael Albinus
2020-12-11 11:29 ` APEL Martin
2020-12-11 11:52 ` Michael Albinus
2020-12-13 16:04 ` Michael Albinus
2020-12-15 11:37 ` Michael Albinus
2020-12-15 12:45 ` APEL Martin
2020-12-15 14:37 ` Michael Albinus
2020-12-15 18:45 ` Michael Albinus
2020-12-16 6:44 ` APEL Martin
2020-12-16 15:34 ` Michael Albinus
2020-12-16 15:55 ` APEL Martin
2020-12-17 11:35 ` APEL Martin
2020-12-17 12:50 ` Michael Albinus
2020-12-18 7:48 ` APEL Martin
2020-12-18 12:35 ` Michael Albinus
2020-12-18 12:56 ` APEL Martin
2020-12-18 13:04 ` Michael Albinus
2020-12-18 14:54 ` APEL Martin
2020-12-18 15:00 ` Michael Albinus
2020-12-18 15:10 ` APEL Martin
2020-12-18 15:18 ` Michael Albinus
2020-12-22 14:57 ` Michael Albinus
2021-01-07 11:13 ` APEL Martin
2020-12-19 9:18 ` yyoncho
2020-12-19 16:48 ` Michael Albinus
2020-12-20 14:03 ` Michael Albinus
2021-08-05 1:46 ` Thomas Ross
2021-08-05 6:16 ` Eli Zaretskii
2021-08-07 2:08 ` Thomas Ross
2021-08-05 14:10 ` Stefan Monnier
2021-08-05 15:40 ` Michael Albinus
2021-08-05 16:25 ` Stefan Monnier
2021-08-06 7:13 ` Michael Albinus
2021-08-06 14:46 ` Stefan Monnier
2021-08-07 13:51 ` Michael Albinus
2021-08-07 22:04 ` Stefan Monnier
2021-08-08 14:25 ` Michael Albinus
2021-08-12 18:47 ` Michael Albinus
2021-08-13 12:16 ` Michael Albinus
2021-08-07 2:07 ` Thomas Ross
2021-08-07 13:54 ` Michael Albinus
2021-08-08 14:29 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1nx93nh.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=yyoncho@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).