emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: mc <mc@aiguphonie.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: hiding intrusive target-markups-brackets ++ Re: org-special-keyword face not showing in sublevels anymore since commit 69700e1
Date: Tue, 29 Jul 2014 14:43:48 +0300	[thread overview]
Message-ID: <BC8E01C8-A504-44A7-9349-8E692C9F502C@aiguphonie.com> (raw)
In-Reply-To: <87a97tz98t.fsf@bzg.ath.cx>

Hello again Bastien,

thanx for the fix!

Please allow me to shortly direct your attention to an open, 
still uncommented 'feature request’ addressing an optional
‘fontification' or ‘hiding' of the some kind of intrusive target-markups-brackets ( <<  >> ), 
just like this is done with the org-link brackets ( [[ ]] ).

The first reference that was expressing this desire, I found here:


Or could there be posted some hint how to best hack this as a private solution?

All best,

On 28 Jul 2014, at 17:04, Bastien <bzg@gnu.org> wrote:

> Hi Martin,
> mc <mc@aiguphonie.com> writes:
>> 2nd screenshot 
>>     org-special-keyword_face_example_after_commit_69700e1.png
>> shows all ‘COMMENT’ keywords as grey only at the top outline level. 
>> I hope this clarifies the case.
> Yes it does!  This is now fixed, thanks,
> -- 
> Bastien

  reply	other threads:[~2014-07-29 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 16:59 org-special-keyword face not showing in sublevels anymore since commit 69700e1 Martin Carlé
2014-07-25 14:52 ` Sebastien Vauban
2014-07-28 12:49   ` mc
2014-07-28 14:04     ` Bastien
2014-07-29 11:43       ` mc [this message]
2014-07-29 15:18         ` hiding intrusive target-markups-brackets ++ " Bastien
2014-08-04 11:23           ` Gaston Tridoulos

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:

  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=BC8E01C8-A504-44A7-9349-8E692C9F502C@aiguphonie.com \
    --to=mc@aiguphonie.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).