emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: mc <mc@aiguphonie.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-special-keyword face not showing in sublevels anymore since commit 69700e1
Date: Mon, 28 Jul 2014 15:49:36 +0300	[thread overview]
Message-ID: <3BEF181A-7F12-48B0-8E84-87B7306B05BA@aiguphonie.com> (raw)
In-Reply-To: <86zjfx5w3y.fsf@somewhere.org>

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

Hello Seb, 

nice that you come back to this issue.

I don’t know what “an ECM” is, but I attach you a simple org file and two screenshots that exemplify the case. 

1st screenshot
    org-special-keyword_face_example_after_commit_69700e1.png
shows all ‘COMMENT’ keywords correctly rendered by the org-special-keyword face as colour grey. 

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.

All best,
mc


[-- Attachment #2: org-special-keyword_face_example.org --]
[-- Type: application/octet-stream, Size: 271 bytes --]

* COMMENT top level -> keyword 'COMMENT' is shown by org-special-keyword face (grey in this case)
** COMMENT second level -> keyword 'COMMENT' is NOT shown by org-special-keyword face
*** COMMENT third level ->  keyword 'COMMENT' is NOT shown by org-special-keyword face

[-- Attachment #3: org-special-keyword_face_example_before_commit_69700e1.png --]
[-- Type: image/png, Size: 17496 bytes --]

[-- Attachment #4: Type: text/plain, Size: 1 bytes --]



[-- Attachment #5: org-special-keyword_face_example_after_commit_69700e1.png --]
[-- Type: image/png, Size: 17089 bytes --]

[-- Attachment #6: Type: text/plain, Size: 630 bytes --]


On 25 Jul 2014, at 17:52, Sebastien Vauban <sva-news@mygooglest.com> wrote:

> Martin Carlé wrote:
>> It appears that by commit 69700e1 [22.04.2014 13:09] a little bug
>> slipped into the codebase, sinc the org-special-keyword face is only
>> shown at the top level in the correct face, but then gets simply
>> overwritten by the respective sublevel face. 
> 
> I did not understand exactly what you meant by sublevel face. Could you
> explain more accurately, maybe with an ECM and a screenshot of how it
> was before and after the above commit?
> 
> Best regards,
>  Seb
> 
> -- 
> Sebastien Vauban
> 
> 


  reply	other threads:[~2014-07-28 12:50 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 [this message]
2014-07-28 14:04     ` Bastien
2014-07-29 11:43       ` hiding intrusive target-markups-brackets ++ " mc
2014-07-29 15:18         ` 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:
  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=3BEF181A-7F12-48B0-8E84-87B7306B05BA@aiguphonie.com \
    --to=mc@aiguphonie.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.com \
    /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).