From: Philipp Stephani <p.stephani2@gmail.com>
To: 24709@debbugs.gnu.org
Subject: bug#24709: 26.0.50; Support for Markdown in electric-quote-mode
Date: Sun, 02 Jul 2017 15:49:13 +0000 [thread overview]
Message-ID: <CAArVCkSzvx5Eqk2ApfWbHufSsmqbonBzJp+U+86PbEnuWdkJEw@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkQBkN=s8HNEDF=ptp-0EgeEMK4v0vzrumBZo08BNBmLuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Philipp Stephani <p.stephani2@gmail.com> schrieb am Mi., 28. Juni 2017 um
23:59 Uhr:
> Philipp Stephani <p.stephani2@gmail.com> schrieb am So., 16. Okt. 2016 um
> 19:22 Uhr:
>
>>
>> When editing a Markdown document with electric-quote-mode enabled, the
>> experience is not optimal because ` (backtick) in Markdown is a syntax
>> element (for introducing code spans and blocks), but is converted by
>> electric-quote-mode. Also ` and ' inside code spans and blocks continue
>> to insert curly quotes where they shouldn't. I propose the following:
>>
>> - Provide an alternative behavior of electric-quote-mode where ` doesn't
>> trigger replacement and ' can insert left or right curly quotes,
>> depending on whether it follows a space or similar (newline, beginning
>> of buffer, opening parenthesis).
>>
>> - Provide a way to disable electric-quote-mode for certain regions,
>> effectively the inverse of the existing electric-quote-string etc.
>> This could be in the form of syntactic elements or text properties.
>>
>>
>>
> I've attached a patch. It doesn't cover all cases, though; e.g. an
> unterminated Markdown code span is not supported yet.
>
Pushed as 34d4720f83.
[-- Attachment #2: Type: text/html, Size: 1866 bytes --]
next prev parent reply other threads:[~2017-07-02 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 17:19 bug#24709: 26.0.50; Support for Markdown in electric-quote-mode Philipp Stephani
2016-10-19 11:10 ` Alan Third
2017-06-28 21:59 ` Philipp Stephani
2017-07-02 15:49 ` Philipp Stephani [this message]
2017-07-02 16:20 ` Philipp Stephani
2017-07-09 19:57 ` Philipp Stephani
2017-07-14 12:36 ` 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=CAArVCkSzvx5Eqk2ApfWbHufSsmqbonBzJp+U+86PbEnuWdkJEw@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=24709@debbugs.gnu.org \
/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.