From: Alain.Cochard@unistra.fr
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem in removing the invisible brackets of a link
Date: Tue, 3 Jul 2018 15:12:15 +0200 [thread overview]
Message-ID: <23355.30255.900844.106396@frac.u-strasbg.fr> (raw)
In-Reply-To: <87r2kpyane.fsf@nicolasgoaziou.fr>
Nicolas Goaziou writes on Fri 29 Jun 2018 15:39:
> > The manual says:
> >
> > If you place the cursor at the beginning or just behind the end
> > of the displayed text and press <BACKSPACE>, you will remove the
> > (invisible) bracket at that location.
> >
> > The problem for me it that it depends on the way I arrive at those
> > locations. For example, for '[[xx]]', seen as 'xx' underlined, if I
> > have the cursor on the right of it and have it go towards the left
> > just after the second 'x' and press <BACKSPACE>, then the behavior is
> > as I expect (I see '[[xx]'), but, if I have the cursor on the left and
> > have it go to towards the right just after the second 'x' and press
> > <BACKSPACE>, then I see a single underlined 'x' (after a second
> > <BACKSPACE> I see '[[]]').
> >
> > Is this normal? [...]
> Yes, it is normal Emacs behaviour. See (info "(elisp) Invisible
> Text").
OK, thanks a lot.
> I guess we could clarify the manual. Suggestions welcome.
I guess you could simply add a footnote after "location." in the
excerpt above.
- Minimalist: See (info "(elisp) Invisible Text").
- Hardly more: For more details, see (info "(elisp) Invisible Text").
- Facetious: If unexpected behavior occurs, check (info "(elisp)
Invisible Text").
- Too kind: Beware, the precise behavior depends on how the cursor has
been placed there -- see (info "(elisp) Invisible Text").
> > Incidentally, is there a way to have things like [[xx]] behave as
> > plain text?
> Yes, there is. Insert a zero width space after the opening
> brackets.
Thanks again. I would also advocate some mention of this in the
manual (if not already there somewhere, which I did not find). I was
thinking about an extra sentence at the end of "4.1 Link format";
something like:
To have ‘[[text]]’ constructs behave as plain text and not as
links, insert a zero-width space (C-x 8 <RET> ZERO WIDTH SPACE
<RET>) between the opening (or the closing) brackets.
However, I still don't see how this can be something convenient for
massive and frequent use. In my case, I often yank and work on code
fragments written in the Mathematica language, for which the [[]]
syntax is used for list indexing. Well, I guess I'll have to learn to
live with that...
> > (I am not talking about literal links which are still
> > understood as links.) I have tried 'quote', 'verse', 'verbatim',
> > 'comment', 'example', and org code block: none work.
> =[[xx]]= and ~[[xx]]= are not links; try to export them.
Indeed. Thanks once more.
Regards
--
EOST (École et Observatoire des Sciences de la Terre)
IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | Fax: +33 (0)3 68 85 01 25
next prev parent reply other threads:[~2018-07-03 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 9:36 Problem in removing the invisible brackets of a link Alain.Cochard
2018-06-29 13:39 ` Nicolas Goaziou
2018-07-03 13:12 ` Alain.Cochard [this message]
2018-10-14 8:07 ` Nicolas Goaziou
2018-10-14 12:11 ` Kaushal Modi
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=23355.30255.900844.106396@frac.u-strasbg.fr \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).