From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stephen Berman <stephen.berman@gmx.net>, 70984@debbugs.gnu.org
Subject: bug#70984: 30.0.50; Improved support for entering quotation marks, Re: bug#70984: 30.0.50; Improved support for entering quotation marks
Date: Fri, 17 May 2024 09:45:14 +0200 [thread overview]
Message-ID: <87msooj305.fsf@gmail.com> (raw)
In-Reply-To: <86cypliwf5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 May 2024 18:55:10 +0300, Thu, 16 May 2024 18:05:33 +0200")
>>>>> On Thu, 16 May 2024 18:55:10 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> +*** "latin-prefix" and "latin-postfix" quotation marks additions.
>> +These input methods can now produce single, double and "low" left and
>> +right quotation marks:
>> +"‘", "’", "“", "”", "„", and "‚"
Eli> Why is the last line broken in the middle?
Because I messed up the formatting.
>> +*** "latin-prefix" and "latin-postfix" guillemets support.
>> +These input methods can now produce single guillemets. For
>> +"latin-prefix" use "~~<" and "~~>", for "latin-postfix" use "<~" and
>> +">~". Double guillemets were already supported.
Eli> Suggest to show the guillemets themselves: not sure everyone knows
Eli> what they are.
Those who need to use them know what they are 😀, but Iʼll add them in
anyway.
Eli> Are any of these worthy of being mentioned in the user manual (the
Eli> "Inserting Text" node)?
I donʼt think so. I do plan to mention them in the manual when I
extend `electric-quote-chars'.
>>>>> On Thu, 16 May 2024 18:05:33 +0200, Stephen Berman <stephen.berman@gmx.net> said:
Stephen> I spotted a couple of typos and stylistic infelicities (IMO):
Thanks, all fixed.
Iʼm assuming this means youʼre both ok with the key sequences I chose.
Robert
--
next prev parent reply other threads:[~2024-05-17 7:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 14:35 bug#70984: 30.0.50; Improved support for entering quotation marks Robert Pluim
2024-05-16 15:55 ` Eli Zaretskii
2024-05-17 7:45 ` Robert Pluim [this message]
2024-05-17 8:21 ` bug#70984: 30.0.50; Improved support for entering quotation marks, " Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 8:59 ` Robert Pluim
2024-05-17 9:59 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 12:10 ` Robert Pluim
2024-05-17 12:53 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 13:15 ` Robert Pluim
2024-05-17 13:21 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-03 11:33 ` Robert Pluim
2024-05-17 10:44 ` Eli Zaretskii
2024-05-17 12:15 ` Robert Pluim
2024-05-17 13:05 ` Eli Zaretskii
2024-05-17 13:27 ` Robert Pluim
2024-05-17 13:38 ` Eli Zaretskii
2024-05-17 15:41 ` Robert Pluim
2024-05-18 10:57 ` Eli Zaretskii
2024-05-16 16:05 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87msooj305.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=70984@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.net \
/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.