From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: bug?
Date: Sat, 01 Jul 2017 14:30:13 +0200 [thread overview]
Message-ID: <87vanc2vca.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m260fethxb.fsf@andrew.cmu.edu> (John Kitchin's message of "Thu, 29 Jun 2017 20:53:20 -0400")
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> All I thought should happen is that the invisible text adjacent to the
> point would be edited (except for the {}). Other than the edge case
> where there is no first headline, it seems to work ok as far as I can
> tell.
Oops. I thought I had fixed it, but it wasn't the case. Done now.
My question is still open: what could this function do, if anything,
close to invisible text per properties (i.e., a link or
sub/superscript)?
I'm not even sure there is something clever to do. A few months ago,
I wanted to solve the problem differently, and suggested to display
"[[path][desc]]" as "[desc]" instead of just "desc". It wasn't so well
received. Admittedly, it adds cruft to the buffer.
Someone suggested to have the link expand whenever the point was over
it, but it was a time-consuming process and it would cause the text to
jump around.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-07-01 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 13:38 bug? John Kitchin
2017-06-29 14:36 ` bug? Nicolas Goaziou
2017-06-30 0:53 ` bug? John Kitchin
2017-07-01 12:30 ` Nicolas Goaziou [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-06 14:47 Bug?? Susan Cragin
2014-05-06 15:28 ` Bug?? Maurice
2014-05-06 21:30 ` Bug?? Suvayu Ali
2014-05-07 16:15 ` Bug?? Achim Gratz
2014-02-06 10:15 Bug: "#+STARTUP: content" shows text as well as headlines [8.2.5h (8.2.5h-elpa @ ~/.emacs.d/elpa/org/) Paul Stansell
2014-02-06 10:42 ` Bastien
2014-02-06 11:38 ` Bastien
2014-03-06 17:32 ` Bug: Paul Stansell
2012-12-04 16:53 Bug? Charles
2012-12-04 19:12 ` Bug? Achim Gratz
2012-12-05 1:20 ` Bug? Charles
2010-05-12 12:50 bug? J. David Boyd
2010-05-12 13:35 ` bug? Bernt Hansen
2010-05-12 14:32 ` bug? J. David Boyd
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vanc2vca.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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/org-mode.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).