unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kishore Rathinavel <kishore.r.318@gmail.com>
To: Peter Dyballa <Peter_Dyballa@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Change .emacs directory in Ubuntu
Date: Wed, 4 Sep 2013 21:43:04 -0400	[thread overview]
Message-ID: <CAKiqZ87WFE_rFixT87s9tFeUz1eSsaJc2AdqqAHd6iNtuNm6nA@mail.gmail.com> (raw)
In-Reply-To: <2B3E4284-0852-4DBA-A09D-CAB9FA2E690B@web.de>

@Steven: That doesnt solve my problem of trying to keep all emacs related
files within the same folder, while seperating them from the other files in
HOME folder. The reason I like it this way is so that I dont need to bother
finding out which files to copy when I move between differnt OS
installations.

@Peter:
Sorry that I didnt realize that was a single command entirely.
I tried:
$ env EMACSLOADPATH=~/EmacsHome emacs

and it opens emacs with an error in the minibar which reads: byte-code:
Cannot open load file: warnings
and in the terminal there is an error that reads: could not find simple.el

But, I have placed the same .emacs in both the folders - the HOME as well
as EmacsHome

So, I tried C-x C-f ~/.emacs and I modified the first string so that I can
find out which .emacs is being modified - and its the one in the HOME
folder.




On Wed, Sep 4, 2013 at 8:22 PM, Peter Dyballa <Peter_Dyballa@web.de> wrote:

>
> Am 05.09.2013 um 01:12 schrieb Kishore Rathinavel:
>
> > Anyways, I tried opening Emacs after the executing the 2nd command above,
> > and I have the same problem still.
>
> *On ONE line* you first set the additional environment variable and then
> launch GNU Emacs.
>
> I gave the full recipe.
>
> There exist ways to set an environment variable persistently.
>
> --
> Greetings
>
>   Pete
>
> If it should exist, it doesn't.
>                                 – Arnold's First Law of Documentation
>
>


  reply	other threads:[~2013-09-05  1:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 20:37 Change .emacs directory in Ubuntu kishore.r.318
2013-09-04 22:24 ` Peter Dyballa
2013-09-04 22:45   ` Kishore Rathinavel
2013-09-04 22:58     ` Peter Dyballa
2013-09-04 23:12       ` Kishore Rathinavel
2013-09-05  0:22         ` Peter Dyballa
2013-09-05  1:43           ` Kishore Rathinavel [this message]
2013-09-05  8:40             ` Peter Dyballa
2013-09-05 16:34             ` Suvayu Ali
     [not found]           ` <mailman.1329.1378345390.10748.help-gnu-emacs@gnu.org>
2013-09-05  2:47             ` Rustom Mody
2013-09-04 23:35 ` Steven Knight
2013-09-05  0:35 ` Suvayu Ali
     [not found] ` <mailman.1321.1378333498.10748.help-gnu-emacs@gnu.org>
2013-09-05  9:11   ` Joost Kremers
2013-09-05  9:19 ` Joost Kremers
2013-09-05  9:31   ` Eli Zaretskii
2013-09-05  9:32   ` Peter Dyballa
2013-09-05 16:58     ` Kishore Rathinavel
  -- strict thread matches above, loose matches on Subject: below --
2013-09-05 10:41 Vilibald Wanca

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=CAKiqZ87WFE_rFixT87s9tFeUz1eSsaJc2AdqqAHd6iNtuNm6nA@mail.gmail.com \
    --to=kishore.r.318@gmail.com \
    --cc=Peter_Dyballa@web.de \
    --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).