unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jiajian Huang <wherejoystarts@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24271@debbugs.gnu.org
Subject: bug#24271: 25.1; font-lock problem of c++-mode
Date: Sat, 20 Aug 2016 16:27:38 +0800	[thread overview]
Message-ID: <F5456118-2914-4243-8F4E-A637B1123DF4@gmail.com> (raw)
In-Reply-To: <83k2fbdfg9.fsf@gnu.org>

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

Thanks for your reply.

> The effects of changing the colors is exacerbated in your case by the
> fact that you use a bold face for some of the faces.  

The changes is really annoying. In my opinion, a bold type font for keywords 
and variable name is just too common in modern editor using a large monitor.
With the regular font style, it’s difficult to read the code.

> On 20 Aug 2016, at 16:15, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> Regardless of what Alan, the developer of the C++ mode says about
> this, I think you can avoid at least some of the unpleasant effects of
> this in your setup if you activate stealth fontification by setting
> jit-stealth-time to some non-nil value, like 0.1. 


Do you mean jit-lock-stealth-time ?

I set it to 0.1 (even 0.8) and nothing changes.

Thanks.

[-- Attachment #2: Type: text/html, Size: 4048 bytes --]

  reply	other threads:[~2016-08-20  8:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20  0:42 bug#24271: 25.1; font-lock problem of c++-mode Jiajian Huang
2016-08-20  6:56 ` Eli Zaretskii
     [not found]   ` <1645ABE9-D61A-4DDE-B4D6-94A29A2CC2AA@gmail.com>
2016-08-20  7:52     ` Eli Zaretskii
2016-08-20  7:57     ` Jiajian Huang
2016-08-20  8:15       ` Eli Zaretskii
2016-08-20  8:27         ` Jiajian Huang [this message]
2016-08-20  8:36           ` Eli Zaretskii
2019-11-17  7:08       ` Lars Ingebrigtsen

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F5456118-2914-4243-8F4E-A637B1123DF4@gmail.com \
    --to=wherejoystarts@gmail.com \
    --cc=24271@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.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).