From: Robert Pluim <rpluim@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 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 10:59:57 +0200 [thread overview]
Message-ID: <87ikzcizjm.fsf@gmail.com> (raw)
In-Reply-To: <87r0e0c0i3.fsf@gmx.net> (Stephen Berman's message of "Fri, 17 May 2024 10:21:08 +0200")
>>>>> On Fri, 17 May 2024 10:21:08 +0200, Stephen Berman <stephen.berman@gmx.net> said:
>> Iʼm assuming this means youʼre both ok with the key sequences I chose.
Stephen> As an innocent bystander I was at first puzzled at your choice of 'C-x 8
Stephen> < <' and 'C-x 8 > >' for "‹" and "›", respectively; but then I found
Stephen> that 'C-x 8 <' and 'C-x 8 >' in the global map already produce "«" and
Stephen> "»", presumably because the latter are the real quotation marks in
Stephen> French, while "single guillemets" are less frequently used. So your
Stephen> choice makes sense after all.
Exactly (should I put the existing C-x 8 bindings in the NEWS
entry?).
Iʼm more doubtful about my choices for the German quotation marks in
the C-x 8 map. They correspond to the keys that have '(' and ')' on
the US keyboard, but not the German standard keyboard, but theyʼre
easy to type on both layouts. I could put them on 'C-x 8 8' and 'C-x 8
9', since those can produce '[' and ']' in the German layout, which is
kind of mnemonic. (The official German layout has them on 2nd or 3rd
level shift variants of 'x' and 'v', which I thought was too
convoluted to emulate).
Robert
--
next prev parent reply other threads:[~2024-05-17 8:59 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 ` bug#70984: 30.0.50; Improved support for entering quotation marks, " Robert Pluim
2024-05-17 8:21 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 8:59 ` Robert Pluim [this message]
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=87ikzcizjm.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.