From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: How to quit?
Date: Fri, 27 Feb 2015 01:53:16 +0100 [thread overview]
Message-ID: <874mq89nur.fsf@debian.uxu> (raw)
In-Reply-To: mailman.849.1424906531.31049.help-gnu-emacs@gnu.org
Drew Adams <drew.adams@oracle.com> writes:
> Just put `(top-level)' in your init file where you
> want it to stop. Command `top-level' returns to,
> well, Emacs top-level. ;-)
Yes, that seems to do exactly what the OP wants.
> But really you will find, I think, that
> commenting-out blocks of the file is the handiest. I
> bind `C-x C-;' to `comment-region', which comments
> or (with `C-u') uncomments the region, and which
> nests and unnests such commented blocks (unlike
> `comment-dwim').
I don't like the idea of commenting out code blocks.
The code will be hard to read as code (as a comment!?)
with no font lock (or worse: the same color as the
"real" comments which are now drowned). It'll just be
bulky and in the way.
I have a better idea, and that is for the OP to split
his init file into several files all dedicated a
specific area of configuration and/or extention. The
OP mentioned 900 lines of Elisp - myself, I use
several files and very few are longer than 100 lines
(those which are often has ambitious documentation
inline which makes for a huge bulk of lines).
Besides many other advantages, in this specific
situation, one could load all the files from .emacs
(with `load-file') and then just comment out a single
line to not have a specific file loaded.
--
underground experts united
next prev parent reply other threads:[~2015-02-27 0:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 15:36 How to quit? Marcin Borkowski
2015-02-25 16:07 ` Doug Lewan
2015-02-25 16:24 ` Marcin Borkowski
2015-02-25 16:19 ` Thien-Thi Nguyen
[not found] ` <mailman.810.1424880439.31049.help-gnu-emacs@gnu.org>
2015-02-25 17:11 ` Emanuel Berg
2015-02-25 17:57 ` J. David Boyd
2015-02-25 18:55 ` Marcin Borkowski
2015-02-25 18:54 ` Bob Proulx
2015-02-25 23:21 ` Drew Adams
2015-02-26 1:29 ` Robert Thorpe
[not found] ` <mailman.849.1424906531.31049.help-gnu-emacs@gnu.org>
2015-02-27 0:53 ` Emanuel Berg [this message]
2015-02-27 3:33 ` Drew Adams
[not found] ` <mailman.909.1425008047.31049.help-gnu-emacs@gnu.org>
2015-02-27 19:09 ` Emanuel Berg
[not found] <mailman.808.1424878616.31049.help-gnu-emacs@gnu.org>
2015-02-25 23:08 ` unfrostedpoptart
[not found] <mailman.854.1424914176.31049.help-gnu-emacs@gnu.org>
2015-02-27 0:56 ` Emanuel Berg
2015-02-27 2:57 ` Robert Thorpe
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=874mq89nur.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.