From: Michael Brand <michael.ch.brand@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Link "bracket-types"
Date: Thu, 10 May 2018 15:23:51 +0200 [thread overview]
Message-ID: <CALn3zoh+5HEF=DpT0zQaoMCQdQjm82VERt7Y1+9dFF6cVFihyw@mail.gmail.com> (raw)
In-Reply-To: <87603vr86w.fsf@nicolasgoaziou.fr>
Hi Nicolas
On Thu, May 10, 2018 at 2:44 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> I still don't understand what your use case is about. Why do you care
> about the presence of square brackets?
Because I care about the raw file content that I see when using
non-Org tools like mainly git but also diff, grep, less, vi and
whatever.
> It is difficult to think about the pertinence of a solution if the
> problem is not well defined.
I could use org-descriptive-links nil to make the brackets visible.
But I would prefer a compromise like I mentioned in my last post: Case
1 like with org-descriptive-links t and case 3/4 like with
org-descriptive-links nil.
Michael
next prev parent reply other threads:[~2018-05-10 13:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 6:08 Link "bracket-types" Michael Brand
2018-05-10 8:14 ` Nicolas Goaziou
2018-05-10 8:32 ` Eric S Fraga
2018-05-11 12:34 ` Nicolas Goaziou
2018-05-11 13:20 ` Eric S Fraga
2018-05-10 9:41 ` Michael Brand
2018-05-10 12:44 ` Nicolas Goaziou
2018-05-10 13:23 ` Michael Brand [this message]
2018-05-10 13:33 ` Nicolas Goaziou
2018-05-10 14:29 ` Michael Brand
2018-05-10 16:27 ` Nicolas Goaziou
2018-05-10 19:58 ` Samuel Wales
2018-05-12 23:35 ` Samuel Wales
2018-05-13 11:10 ` Eric S Fraga
2018-05-10 19:59 ` Michael Brand
2018-05-11 0:22 ` Nicolas Goaziou
2018-05-11 13:10 ` Nicolas Goaziou
2018-05-11 13:55 ` Michael Brand
2018-05-11 14:15 ` Nicolas Goaziou
2018-05-12 8:12 ` Michael Brand
2018-05-17 16:17 ` Michael Brand
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='CALn3zoh+5HEF=DpT0zQaoMCQdQjm82VERt7Y1+9dFF6cVFihyw@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--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 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.