unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: porting crufty old init.el to package management
Date: Mon, 24 Mar 2014 09:25:31 +0100	[thread overview]
Message-ID: <87txaovw90.fsf@gmail.com> (raw)
In-Reply-To: 8738i8pjux.fsf@pobox.com

Tom Roche <Tom_Roche@pobox.com> writes:

> I'm wondering, would anyone care to recommend especially worthy docs
> for this process (guides, howto's, tutorials)? esp how best to
> accommodate snippets of elisp (gists?)

If you think of your init file more as '(comment)text with code',
Org-Babel and the associated starter-kit
(http://eschulte.github.io/emacs-starter-kit/) are definitely worth a
try. 

OTOH, if you think of your init file more as 'code with (comment)text',
then using outshine.el might be more comfortable
(http://orgmode.org/worg/org-tutorials/org-outside-org.html). 

Here is how I currently structure my init.el with outshine headlines
(that allow for much of Org-mode's navigation, visibility cycling and
structure editing functionality):

,-----------------------------------------------------
| 98 matches for "^;; \*\*?\*?\*? " in buffer: init.el
|       1:;; * init.el --- Emacs Init File (TJ)
|       5:;; * Begin Startup
|      16:;; * General Configurations
|      20:;; ** Coding System
|      30:;; ** Screen Colors
|      50:;; ** Global Settings
|      80:;; ** Global Keys
|      91:;; ** Define Aliases
|     114:;; ** Load Path
|     116:;; *** Load-Path Enhancement
|     150:;; *** Library Search
|     201:;; ** Package Manager
|     207:;; * Helper functions
|     211:;; ** Improved Require
|     236:;; ** Idle Require
|     262:;; ** Fast Temporary Buffers
|     272:;; ** Elisp Symbols
|     331:;; ** Files and Directories
|     357:;; ** Window Split
|     408:;; ** Scratch Buffer
|     419:;; ** Truncate Lines
|     431:;; ** Recentf with Ido
|     453:;; * Major Modes
|     457:;; ** Org
|     461:;; *** General
|     463:;; **** Configuration
|     508:;; **** Functions
|     545:;; *** Hyperlinks
|     547:;; **** Configuration 
|     556:;; *** Properties and Columns
|     558:;; **** Configuration 
|     568:;; *** Exporting
|     570:;; **** Configuration 
|     577:;; *** Timestamps
|     579:;; **** Configuration 
|     584:;; **** Functions
|     607:;; *** Tags
|     609:;; **** Configuration 
|     639:;; *** Clocking
|     641:;; **** Configuration 
|     703:;; **** Functions
|     833:;; *** Capturing
|     835:;; **** Configuration
|     861:;; *** Projects
|     863:;; **** Functions
|    1062:;; *** Archiving
|    1064:;; **** Configuration 
|    1069:;; **** Functions
|    1109:;; *** Agenda
|    1111:;; **** Configuration 
|    1352:;; **** Functions
|    1537:;; *** Refile
|    1539:;; **** Configuration 
|    1577:;; **** Functions
|    1585:;; *** Org-Babel
|    1587:;; **** Configuration
|    1651:;; **** Functions
|    1658:;; *** Skeletons
|    1660:;; **** Abbreviations
|    1676:;; **** Definitions
|    1721:;; *** Keybindings
|    1729:;; ** LaTeX
|    1733:;; *** Configuration
|    1821:;; *** Functions
|    1823:;; ** Calendar 
|    1831:;; ** PicoLisp
|    1865:;; ** Slime
|    1912:;; ** Scala
|    1919:;; ** Dired
|    1964:;; ** IRC
|    1980:;; ** Message
|    1986:;; ** Magit
|    1993:;; ** W3M
|    1997:;; *** Configurations
|    2090:;; *** Functions
|    2097:;; ** Ediff
|    2151:;; ** Occur
|    2153:;; *** Configurations
|    2165:;; *** Functions
|    2193:;; * Minor Modes
|    2197:;; ** Outline
|    2221:;; ** Ido
|    2259:;; ** Smex
|    2278:;; ** S
|    2284:;; ** Undo Tree Mode
|    2294:;; ** Rebox2
|    2307:;; ** Rainbow Delimiters
|    2314:;; ** Auto Pair
|    2320:;; ** Eldoc
|    2328:;; ** Logito
|    2335:;; ** Openwith
|    2352:;; ** Workgroups
|    2362:;; ** Switch Windows
|    2368:;; ** Window Numbering
|    2375:;; ** Winner Mode
|    2386:;; ** Nuke'n Eval 
|    2398:;; * End Startup
|    2412:;; * Custom Set Variables/Fonts
`-----------------------------------------------------

-- 
cheers,
Thorsten




  parent reply	other threads:[~2014-03-24  8:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23 23:37 porting crufty old init.el to package management Tom Roche
2014-03-24  3:01 ` Marcin Borkowski
2014-03-24  8:25 ` Thorsten Jolitz [this message]
2014-03-24 12:42   ` Alan Schmitt
  -- strict thread matches above, loose matches on Subject: below --
2014-03-24 22:30 Barry OReilly
2014-03-25 18:10 ` Zhen Sun
     [not found] <mailman.17994.1395617870.10748.help-gnu-emacs@gnu.org>
2014-03-24 10:10 ` Fabrice Niessen
2014-03-24 12:41   ` Guido Van Hoecke
     [not found]   ` <mailman.18031.1395664909.10748.help-gnu-emacs@gnu.org>
2014-03-24 14:13     ` Fabrice Niessen
2014-03-24 20:01       ` Guido Van Hoecke
     [not found]       ` <mailman.18082.1395691327.10748.help-gnu-emacs@gnu.org>
2014-03-24 20:05         ` Fabrice Niessen
2014-03-24 20:39           ` Guido Van Hoecke
     [not found]           ` <mailman.18086.1395693586.10748.help-gnu-emacs@gnu.org>
2014-03-24 22:38             ` Fabrice Niessen
2014-03-25  2:01               ` Stefan
2014-03-25 10:27                 ` Guido Van Hoecke
2014-04-18  6:57   ` Brady Trainor
2014-03-26  3:42 ` Rusi
2014-03-26 11:22   ` Neal Becker
2014-03-26 17:55   ` jpkotta
2014-04-18  6:47   ` Brady Trainor

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=87txaovw90.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --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).