From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Re: How to handle overfilled mode line?
Date: Thu, 05 Oct 2006 21:08:48 +0200 [thread overview]
Message-ID: <87k63einr3.fsf@baldur.nicundtas.de> (raw)
In-Reply-To: t90gv3-v0c.ln1@xword.teksavvy.com
"Chris F.A. Johnson" <cfajohnson@gmail.com> writes:
Hi Chris,
> Use a file name instead of a précis!
What's a "précis"?
Bye,
Tassilo
--
"Emacs is not a development tool but a way of life."
- David Kastrup in alt.religion.emacs -
next prev parent reply other threads:[~2006-10-05 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 22:42 How to handle overfilled mode line? Tassilo Horn
2006-10-05 15:18 ` rgb
2006-10-05 16:15 ` robert.thorpe
2006-10-05 17:15 ` Tassilo Horn
2006-10-05 18:42 ` Chris F.A. Johnson
2006-10-05 19:08 ` Tassilo Horn [this message]
2006-10-05 19:50 ` Pascal Bourguignon
2006-10-05 22:16 ` Reiner Steib
2006-10-06 12:13 ` Tassilo Horn
2006-10-06 13:39 ` Kim F. Storm
[not found] ` <mailman.7811.1160142023.9609.help-gnu-emacs@gnu.org>
2006-10-06 14:17 ` Tassilo Horn
2006-10-06 15:57 ` Kevin Rodgers
[not found] ` <mailman.7822.1160150374.9609.help-gnu-emacs@gnu.org>
2006-10-06 18:49 ` Tassilo Horn
2006-10-05 16:58 ` Michaël Cadilhac
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=87k63einr3.fsf@baldur.nicundtas.de \
--to=heimdall@uni-koblenz.de \
/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).