From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: dan.colascione@gmail.com, 19946@debbugs.gnu.org,
jostein@secure.kjonigsen.net, simenheg@gmail.com,
dgutov@yandex.ru, jostein@kjonigsen.net
Subject: bug#19946: 24.4; js-mode, indentation
Date: Sun, 03 Apr 2016 21:17:20 +0300 [thread overview]
Message-ID: <83mvpapnf3.fsf@gnu.org> (raw)
In-Reply-To: <m2bn5qlg93.fsf@newartisans.com> (message from John Wiegley on Sun, 03 Apr 2016 11:05:44 -0700)
> From: John Wiegley <jwiegley@gmail.com>
> Date: Sun, 03 Apr 2016 11:05:44 -0700
> Cc: dan.colascione@gmail.com, 19946@debbugs.gnu.org,
> Simen Heggestøyl <simenheg@gmail.com>,
> Dmitry Gutov <dgutov@yandex.ru>, jostein@kjonigsen.net
>
> >>>>> Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:
>
> > If we should at least attempt to adhere to the principle of least
> > astonishment, we need to either accept \r\n patches everywhere or change the
> > semantics of $ to also include \r, line-break format be damned.
>
> What if there were another buffer coding system called "broken-msdos" or
> something, that accepted mixed \n and \r\n, but wrote out all \r\n? I run
> into such files often enough.
We already have that, it's called "dos".
next prev parent reply other threads:[~2016-04-03 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 10:09 bug#19946: 24.4; js-mode, indentation Jostein Kjønigsen
2016-03-19 22:13 ` Simen Heggestøyl
2016-03-20 1:27 ` Dmitry Gutov
2016-03-20 8:25 ` Andreas Schwab
2016-03-20 19:01 ` Jostein Kjønigsen
2016-03-20 19:02 ` Daniel Colascione
2016-03-20 19:15 ` Jostein Kjønigsen
2016-04-03 18:05 ` John Wiegley
2016-04-03 18:17 ` Eli Zaretskii [this message]
2016-03-20 19:18 ` Dmitry Gutov
2016-03-20 19:47 ` Jostein Kjønigsen
2016-03-20 19:49 ` Dmitry Gutov
2016-03-21 0:08 ` Daniel Colascione
2016-03-21 0:32 ` Dmitry Gutov
2020-08-25 9:48 ` Lars Ingebrigtsen
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=83mvpapnf3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19946@debbugs.gnu.org \
--cc=dan.colascione@gmail.com \
--cc=dgutov@yandex.ru \
--cc=jostein@kjonigsen.net \
--cc=jostein@secure.kjonigsen.net \
--cc=jwiegley@gmail.com \
--cc=simenheg@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 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.