From: Peter Dyballa <Peter_Dyballa@web.de>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: blue underscores
Date: Wed, 19 Dec 2007 12:57:58 +0100 [thread overview]
Message-ID: <E8317D87-AE44-4B95-AF04-F428A0FFC379@web.de> (raw)
In-Reply-To: <200712191254.17860.andreas.roehler@online.de>
Am 19.12.2007 um 12:54 schrieb Andreas Röhler:
> Meanwhile I see a much better way is to customize
>
> Nobreak Space face
>
> setting Underline value menue to OFF
Isn't this just cheating? Is it handled by tabify the same way as
real SPACE characters?
--
Mit friedvollen Grüßen
Pete
Upgraded, adj.:
Didn't work the first time.
next prev parent reply other threads:[~2007-12-19 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 9:09 blue underscores Andreas Röhler
2007-12-19 10:24 ` Peter Dyballa
2007-12-19 11:22 ` Andreas Röhler
2007-12-19 11:53 ` Peter Dyballa
2007-12-19 11:54 ` Andreas Röhler
2007-12-19 11:57 ` Peter Dyballa [this message]
2007-12-19 13:30 ` Andreas Röhler
2007-12-19 13:59 ` Peter Dyballa
2007-12-19 20:27 ` Andreas Röhler
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=E8317D87-AE44-4B95-AF04-F428A0FFC379@web.de \
--to=peter_dyballa@web.de \
--cc=andreas.roehler@online.de \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).