From: Ted Zlatanov <tzz@lifelogs.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 19145@debbugs.gnu.org, Ken Mankoff <mankoff@gmail.com>
Subject: bug#19145: 24.4; prettify-symbols-mode inconsistent behavior
Date: Tue, 25 Nov 2014 04:49:11 -0500 [thread overview]
Message-ID: <87tx1n4nl4.fsf@lifelogs.com> (raw)
In-Reply-To: <jwvwq6ksljd.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 24 Nov 2014 09:53:43 -0500")
On Mon, 24 Nov 2014 09:53:43 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
SM> Duh! Sorry, I somehow failed to see "python-mode" in your original
SM> bug report. So yes, you're trying to prettify subparts of identifiers,
SM> and prettify-symbols-mode currently provides no support at all for that.
...
SM> But w.r.t "delta" in "delta_x" it would make a lot of sense for
SM> prettify-symbols-mode to provide support for that.
I don't think it would--I would keep `prettify-symbols-mode' strict. I
think Ken needs a different mode that's yet to be written:
`prettify-regex-mode'?
"delta_x" is an entirely different thing from "delta" in all the
programming languages I can think of, so I would not expect to see δ_x
all over the code just because I want to prettify deltas themselves. If
anything, it would make finding the real standalone deltas harder.
Ted
next prev parent reply other threads:[~2014-11-25 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 17:40 bug#19145: 24.4; prettify-symbols-mode inconsistent behavior Ken Mankoff
2014-11-21 18:15 ` Stefan Monnier
2014-11-21 19:22 ` Ken Mankoff
2014-11-22 16:23 ` Stefan Monnier
2014-11-22 23:57 ` Ken Mankoff
2014-11-24 14:53 ` Stefan Monnier
2014-11-25 9:49 ` Ted Zlatanov [this message]
2014-11-25 14:51 ` Stefan Monnier
2014-11-25 15:17 ` Ted Zlatanov
2014-11-25 17:36 ` Stefan Monnier
2014-11-25 18:53 ` Ted Zlatanov
2014-11-26 2:23 ` Stefan Monnier
2014-11-25 14:53 ` Ken Mankoff
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=87tx1n4nl4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=19145@debbugs.gnu.org \
--cc=mankoff@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
/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.