From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
Oleh Krehel <ohwoeowho@gmail.com>,
emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim
Date: Wed, 2 Sep 2015 14:16:28 +0300 [thread overview]
Message-ID: <55E6DA8C.1030403@yandex.ru> (raw)
In-Reply-To: <jwvfv2xd08s.fsf-monnier+emacs@gnu.org>
On 09/02/2015 05:34 AM, Stefan Monnier wrote:
> W.r.t ambiguity, the main problem I see is that we currently can never
> be sure that when we see a ` followed by a ' the two actually form a pair.
> A human usually can tell, but a program can't get it right 100% of the time.
Okay. But then, there's no problem in using the same quoting for key
sequences, aside from the quote-matching algorithm.
>> We might also want to support code snippets like `(progn (foo bar foo))'.
>> At least, elisp-completion-at-point relies on snippets being quoted
>> that way now. We can detect these using paired parens.
>
> Not sure I want to go down that road. What about `(foo 'a 'b)' ?
That, too. At least if this quote-matching logic is implemented in
Elisp, forward-sexp can take care of skipping the spaces.
> AFAIK it's not very common (yet?) to quote code that way, and I'm not
> sure we want to get into the habit of quoting it that way. I could see
> the need/advantage of quoting code reliably, but I don't think `...' is
> a good way to do it.
If we take after Markdown (because why not?), it has two methods of
quoting code: one for inline code (also used for references), and one
for code blocks (on separate lines).
It might be a good idea to also have just one quoting method for inline
code. But if you have a better idea for quoting code, that's fine, too.
next prev parent reply other threads:[~2015-09-02 11:16 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150831061236.27796.57762@vcs.savannah.gnu.org>
[not found] ` <E1ZWIKb-0007FR-Kk@vcs.savannah.gnu.org>
2015-08-31 6:26 ` [Emacs-diffs] master b533552 2/5: Documentation fixes re quotes Dmitry Gutov
2015-08-31 6:39 ` Paul Eggert
2015-08-31 6:47 ` Dmitry Gutov
2015-08-31 6:53 ` Paul Eggert
2015-08-31 7:00 ` Dmitry Gutov
2015-08-31 7:13 ` Paul Eggert
2015-09-01 0:03 ` Richard Stallman
2015-09-02 1:05 ` Paul Eggert
2015-09-02 1:27 ` David Kastrup
2015-09-02 1:30 ` Paul Eggert
2015-09-02 5:19 ` David Kastrup
2015-09-02 5:30 ` Paul Eggert
2015-09-02 15:40 ` Richard Stallman
2015-09-02 16:32 ` David Kastrup
2015-09-03 15:38 ` Dmitry Gutov
2015-09-03 17:42 ` Paul Eggert
2015-09-03 18:49 ` Dmitry Gutov
2015-09-03 21:50 ` Paul Eggert
2015-09-03 22:08 ` Dmitry Gutov
2015-09-03 22:47 ` Paul Eggert
2015-09-03 22:59 ` Dmitry Gutov
2015-09-07 1:28 ` Richard Stallman
[not found] ` <E1ZWIKd-0007Fs-15@vcs.savannah.gnu.org>
2015-08-31 6:29 ` [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim Dmitry Gutov
2015-08-31 6:38 ` Paul Eggert
2015-08-31 17:34 ` Stefan Monnier
2015-08-31 18:40 ` Dmitry Gutov
2015-08-31 18:48 ` Paul Eggert
2015-09-01 7:35 ` David Kastrup
2015-08-31 17:40 ` Stefan Monnier
2015-08-31 18:03 ` Paul Eggert
2015-09-01 1:55 ` Stephen J. Turnbull
2015-09-01 3:40 ` Stefan Monnier
2015-09-01 6:29 ` Paul Eggert
2015-09-01 10:45 ` Oleh Krehel
2015-09-01 10:53 ` Andreas Schwab
2015-09-01 11:22 ` David Kastrup
2015-09-01 11:40 ` Oleh Krehel
2015-09-01 11:42 ` Dmitry Gutov
2015-09-01 12:06 ` David Kastrup
2015-09-01 14:20 ` Dmitry Gutov
2015-09-03 10:16 ` Oleh Krehel
2015-09-03 11:22 ` Dmitry Gutov
2015-09-03 14:50 ` Stefan Monnier
2015-09-03 15:04 ` Dmitry Gutov
2015-09-01 13:31 ` Paul Eggert
2015-09-01 14:15 ` David Kastrup
2015-09-01 15:39 ` Stefan Monnier
2015-09-01 19:00 ` Alan Mackenzie
2015-09-02 4:07 ` Stefan Monnier
2015-09-02 5:28 ` David Kastrup
2015-09-02 10:02 ` Alan Mackenzie
2015-09-02 11:22 ` Dmitry Gutov
2015-09-02 15:41 ` Richard Stallman
2015-09-02 15:53 ` Dmitry Gutov
2015-09-02 16:38 ` Paul Eggert
2015-09-03 15:37 ` Richard Stallman
2015-09-03 17:26 ` Paul Eggert
2015-09-02 16:32 ` Paul Eggert
2015-09-02 17:23 ` Alan Mackenzie
2015-09-02 17:43 ` David Kastrup
2015-09-02 22:25 ` Paul Eggert
2015-09-03 10:48 ` David Kastrup
2015-09-03 12:45 ` Andreas Schwab
2015-09-03 14:46 ` Eli Zaretskii
2015-09-02 22:13 ` Paul Eggert
2015-09-03 12:22 ` Alan Mackenzie
2015-09-03 14:56 ` Paul Eggert
2015-09-04 13:22 ` Alan Mackenzie
2015-09-02 20:14 ` Stefan Monnier
2015-09-01 19:25 ` Paul Eggert
2015-09-07 1:28 ` Richard Stallman
2015-09-01 19:33 ` Dmitry Gutov
2015-09-02 2:34 ` Stefan Monnier
2015-09-02 5:23 ` David Kastrup
2015-09-02 11:16 ` Dmitry Gutov [this message]
2015-09-02 11:52 ` Quoting yank/diff prefixes (was: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim) David Kastrup
2015-09-03 14:34 ` [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim Stefan Monnier
2015-09-01 22:57 ` Richard Stallman
2015-09-01 0:03 ` Richard Stallman
2015-09-01 1:20 ` Paul Eggert
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=55E6DA8C.1030403@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ohwoeowho@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.