emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: Init.el need just for org-mode?
Date: Thu, 3 Nov 2022 06:35:39 +0100	[thread overview]
Message-ID: <Y2NTK9T7itKx57MI@tuxteam.de> (raw)
In-Reply-To: <006CD36B-C555-46B4-AB03-AFADBC05FCEB@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

On Wed, Nov 02, 2022 at 09:15:04PM +0100, Renato Pontefice wrote:
> are You telling that you put more .el files on .emacs.d folder, each one contain some customization of emacs (or org-mode?)
> This is interesting for me.

No. By default, Emacs just loads ~/.emacs.d/init.el /or/ ~/.emacs.

Everything else can be arranged from there. For example, to split
out the custom.el file (where customize writes its stuff), I have
those two lines in my ~/.emacs.d/init.el:

  (setq custom-file "~/.emacs.d/custom.el")
  (load custom-file)

Then, I have a subdirectory of ~/.emacs.d (concretely: ~/.emacs.d/lisp)
where I keep all my local little things I make myself. To be able to
easily load those without always naming the full path, I have in my
~/.emacs.d/init.el:

  (add-to-list 'load-path "~/.emacs.d/lisp")

And so on.

Still I propose you start with an empty init file. Once you find a
thing you /want/ your Emacs to do always at start, you can start
populating your ~/.emacs or ~/.emacs.d/init.el (each approach has
some up- and downsides, but that's not so important: you'll find
out and you'll be able to switch easily).

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-11-03  5:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 17:31 Init.el need just for org-mode? Renato Pontefice
2022-11-02 17:36 ` Jude DaShiell
2022-11-02 17:45   ` Renato Pontefice
2022-11-02 19:28     ` tomas
2022-11-02 19:24   ` tomas
2022-11-02 20:15     ` Renato Pontefice
2022-11-03  5:35       ` tomas [this message]
2022-11-02 20:29 ` Charles Millar
2022-11-02 20:33 ` Charles Millar
2022-11-03 14:04 ` Quiliro Ordóñez
2022-11-03 15:12 ` Max Nikulin

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y2NTK9T7itKx57MI@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-orgmode@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).