From: Jiri Pejchal <jiri.pejchal@gmail.com>
Subject: Re: How big are your customisations?
Date: Sun, 13 Aug 2006 22:22:16 +0200 [thread overview]
Message-ID: <8764gwjshz.fsf@gmail.com> (raw)
In-Reply-To: ebntob$el3$1@reader2.panix.com
dkcombs@panix.com (David Combs) writes:
> In article <mailman.4582.1154078449.9609.help-gnu-emacs@gnu.org>,
> Dieter Wilhelm <dieter@duenenhof-wilhelm.de> wrote:
>>
>>or ... many, many dots ... or Dieter's .emacs has 287 active code
>>lines (575 lines overall, of which the really interesting ones are
>>from a suggestion of Kevin Rogers).
wc -l .emacs
1565 .emacs
It's time to do some cleaning...:-)
--
Jiri Pejchal
next prev parent reply other threads:[~2006-08-13 20:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 9:45 How big are your customisations? Davin Pearson
2006-07-26 10:02 ` David Kastrup
2006-07-26 12:01 ` Tassilo Horn
2006-07-26 12:20 ` Mathias Dahl
2006-07-26 18:52 ` Eli Zaretskii
2006-07-27 12:12 ` Dieter Wilhelm
2006-07-28 16:00 ` Kevin Rodgers
[not found] ` <mailman.4599.1154102463.9609.help-gnu-emacs@gnu.org>
2006-07-28 16:55 ` David Kastrup
2006-07-28 18:18 ` Eric Hanchrow
2006-07-28 18:49 ` Reiner Steib
2006-08-01 14:06 ` Slawomir Nowaczyk
2006-07-27 18:38 ` Edward O'Connor
2006-07-27 19:48 ` Formatting output [was: How big are your customisations?] Dieter Wilhelm
2006-07-28 15:37 ` Formatting output Edward O'Connor
[not found] ` <mailman.4580.1154078436.9609.help-gnu-emacs@gnu.org>
2006-07-29 13:03 ` martin
[not found] ` <mailman.4504.1153939928.9609.help-gnu-emacs@gnu.org>
2006-07-28 9:56 ` How big are your customisations? Davin Pearson
2006-07-28 12:03 ` Checking for Emacs flavors, OS, graphics, ... (was: How big are your customisations?) Reiner Steib
2006-07-28 13:33 ` How big are your customisations? Eli Zaretskii
2006-07-30 1:25 ` David Hansen
[not found] ` <mailman.4652.1154223520.9609.help-gnu-emacs@gnu.org>
2006-08-05 5:28 ` Davin Pearson
2006-08-05 8:22 ` David Hansen
[not found] ` <mailman.4887.1154766208.9609.help-gnu-emacs@gnu.org>
2006-08-05 8:48 ` David Kastrup
2006-08-05 9:34 ` Ralf Angeli
2006-08-05 9:42 ` David Kastrup
2006-08-06 14:53 ` dsoliver
2006-08-06 18:51 ` Eli Zaretskii
[not found] ` <mailman.4592.1154093621.9609.help-gnu-emacs@gnu.org>
2006-08-05 5:43 ` Davin Pearson
2006-08-05 9:53 ` Davin Pearson
2006-08-05 12:15 ` Eli Zaretskii
[not found] ` <mailman.4892.1154780152.9609.help-gnu-emacs@gnu.org>
2006-08-06 4:14 ` Davin Pearson
2006-08-06 5:13 ` Eli Zaretskii
2006-08-06 5:31 ` Eli Zaretskii
[not found] ` <mailman.4913.1154842313.9609.help-gnu-emacs@gnu.org>
2006-08-06 6:04 ` Davin Pearson
[not found] ` <mailman.4907.1154841207.9609.help-gnu-emacs@gnu.org>
2006-08-13 19:09 ` David Combs
2006-08-14 3:24 ` Eli Zaretskii
2006-07-28 14:14 ` robert.thorpe
2006-08-02 9:05 ` Tim X
2006-08-13 19:19 ` David Combs
2006-08-14 8:41 ` Tim X
[not found] ` <mailman.4582.1154078449.9609.help-gnu-emacs@gnu.org>
2006-08-13 19:15 ` David Combs
2006-08-13 20:22 ` Jiri Pejchal [this message]
2006-08-14 20:46 ` Dieter Wilhelm
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=8764gwjshz.fsf@gmail.com \
--to=jiri.pejchal@gmail.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.
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).