unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jarek Czekalski <jarekczek@poczta.onet.pl>
To: emacs-devel@gnu.org
Subject: Re: run/load a lisp script before user init file
Date: Mon, 07 Oct 2013 20:42:43 +0200	[thread overview]
Message-ID: <525300A3.1040506@poczta.onet.pl> (raw)
In-Reply-To: <83a9il58wc.fsf@gnu.org>

W dniu 10/07/2013 06:43 PM, Eli Zaretskii pisze:
> Site init file looks like what you want. Read about it in the "Init 
> File" node of the Emacs User Manual. 

I read the startup procedure. However it still does not seem a clean 
approch. You suggest that I should add a line

(load "emacspeak-loder")

to the site-start, right? But when someone removes emacspeak from 
system, emacs will stop to load correctly. Not nice.

So should I place some multi-line code in site-start, so that it be safe 
to execute? But this is not so easy to do from installer. So this may be 
dangerous too.

What looks interesting is site-start.d directory in Debian. Placing a 
file there could be what I am looking for. But I guess this is not emacs 
solution, but Debian solution. Nothing about site-start.d in emacs 
startup info.

What someone was trying before is to start a script from a command line. 
But we don't have a possibility to specify custom site-start file there. 
What a pity...

Again, does there exist any clean solution? Is there something that I 
could place instead of "load" to make the loading safe in case of a 
missing file? Is there something we could introduce to emacs to make 
things more comfortable?

Jarek



  reply	other threads:[~2013-10-07 18:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 15:24 run/load a lisp script before user init file Jarek Czekalski
2013-10-07 16:43 ` Eli Zaretskii
2013-10-07 18:42   ` Jarek Czekalski [this message]
2013-10-07 19:00     ` Eli Zaretskii
2013-10-07 19:37       ` Jarek Czekalski
2013-10-07 20:08         ` Eli Zaretskii
2013-10-07 22:52           ` Stefan Monnier
2013-10-08  5:52             ` Jarek Czekalski
2013-10-08  6:27               ` Stephen J. Turnbull
2013-10-08  6:40                 ` Harald Hanche-Olsen
2013-10-08 13:09                   ` Stephen J. Turnbull
2013-10-08 14:30                     ` Jarek Czekalski
2013-10-08 14:36                     ` Jarek Czekalski
2013-10-08 14:50                       ` Jarek Czekalski
2013-10-08 16:01                         ` Stephen J. Turnbull
2013-10-08 19:34                         ` Josh
2013-10-08  6:46                 ` Jarek Czekalski
2013-10-08 16:22                   ` Glenn Morris
2013-10-08 17:30                     ` Tom Tromey
2013-10-09  1:56                       ` Stephen J. Turnbull
2013-10-08 21:47                     ` Jarek Czekalski
2013-10-08  6:16       ` Kevin Rodgers
  -- strict thread matches above, loose matches on Subject: below --
2013-10-10 13:52 Barry OReilly
2013-10-10 16:11 ` Josh

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=525300A3.1040506@poczta.onet.pl \
    --to=jarekczek@poczta.onet.pl \
    --cc=emacs-devel@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.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).