From: dbastos@toledo.com (Daniel C. Bastos)
To: info-gnus-english@gnu.org
Subject: Re: A question about Emacs hightlighting!
Date: Mon, 20 Aug 2007 23:24:42 -0400 [thread overview]
Message-ID: <ubqd1in7p.fsf@toledo.com> (raw)
In-Reply-To: <fadjdm$bo8$1@fred.mathworks.com>
"Guofu Chen" <gchen@mathworks.com> writes:
> Hi,
>
> I am now using PuTTY in Windows XP to access Linux. Unfortuantely, I can't
> see the syntax hightlighting for C++ source file. I noticed that the PuTTY
> can
> invoke C++ mode for the C++ source file, but I can't see the C++ syntax
> hightlighting.
>
> Any idea? Thanks!
Do you see syntax highlighting in the other modes?
Here I ran M-x info-apropos and gave it ``global-font-lock-mode'' to
search for. Then I found the font lock mode page. It begins
19.7 Font Lock mode
===================
Font Lock mode is a minor mode, always local to a particular buffer,
which highlights (or "fontifies") the buffer contents according to the
syntax of the text you are editing. It can recognize comments and
strings in most languages; in several languages, it can also recognize
and properly highlight various other important constructs--for example,
names of functions being defined or reserved keywords. Some special
modes, such as Occur mode and Info mode, have completely specialized
ways of assigning fonts for Font Lock mode.
(...)
Check this info page out which will tell you a lot about this type of
customization; as a quick way to try to get the syntax highlighting, try
M-x global-font-lock-mode. But if C++ is the only one that doesn't
highlight, then we need to find out why not and then tell the GNU emacs
to do it.
next prev parent reply other threads:[~2007-08-21 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 2:42 Guofu Chen
2007-08-21 3:24 ` Daniel C. Bastos [this message]
2007-08-21 4:26 ` Daniel Brooks
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=ubqd1in7p.fsf@toledo.com \
--to=dbastos@toledo.com \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).