From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30815@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#30815: 26.0.91; unicode right single quote mark with syntax entry of w not respected by forward-word
Date: Wed, 14 Mar 2018 19:51:11 +0200 [thread overview]
Message-ID: <83r2omr1f4.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48wzdh4517qoeKc8vqxjXoD-vkFGeq7PyNconBRncC=45w@mail.gmail.com> (message from Aaron Jensen on Wed, 14 Mar 2018 10:43:08 -0700)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Wed, 14 Mar 2018 10:43:08 -0700
> Cc: Noam Postavsky <npostavs@gmail.com>, 30815@debbugs.gnu.org
>
> I wanted to change it because I started to use typo-mode:
> https://github.com/jorgenschaefer/typoel which automatically turned
> apostrophes I typed into right quotes in my org-mode files (which is
> where I had it enabled). I was ok with this, but I wanted them to
> behave like apostrophes did (not being word boundaries and all) so I
> went down this path.
>
> I have since unbound ' in that mode, so it just inserts a normal
> apostrophe. I'm aware of the "controversy" surrounding the different
> characters and, to be honest, I can't be bothered. Filing this bug was
> a light weight attempt to see if I was missing something and/or if
> this was unexpected.
>
> For right quote in particular, it's probably even more nuanced. One
> could use right quotes to close a single quoted piece of text. In
> which case, that right quote probably shouldn't be a "word" in the
> syntax table.
>
> Because of all of that, I'm totally happy just using ' like a normal
> person. I'm not an author writing manuscripts.
>
> > The next question is what other characters need this special handling,
> > and how many of them are there?
>
> I do not know. None others that I know of, but that doesn't mean much.
Well, if this is just about ’ , then we could simply change its script
to be 'latin'. But, as you say, that would get in the way with quoted
text.
> I'm happy to consider this issue resolved (I know it's closed and was
> merged into 10494) if everyone else is after the doc changes have been
> merged in.
OK, let's wait for other comments, and consider this resolved if none
come up.
Thanks.
next prev parent reply other threads:[~2018-03-14 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 0:14 bug#30815: 26.0.91; unicode right single quote mark with syntax entry of w not respected by forward-word Aaron Jensen
2018-03-14 1:11 ` Noam Postavsky
2018-03-14 2:07 ` Aaron Jensen
2018-03-14 2:24 ` Noam Postavsky
2018-03-14 2:43 ` Aaron Jensen
2018-03-14 16:09 ` Eli Zaretskii
2018-03-14 17:43 ` Aaron Jensen
2018-03-14 17:51 ` Eli Zaretskii [this message]
2018-03-14 15:59 ` Eli Zaretskii
2018-03-14 23:19 ` Noam Postavsky
2018-03-15 6:39 ` Eli Zaretskii
2018-03-17 0:03 ` Noam Postavsky
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r2omr1f4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30815@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=npostavs@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).