From: bigfaceworm@hotmail.com (bigfaceworm)
Subject: Re: Loading local .emacs from remote machine
Date: 5 Feb 2003 08:33:19 -0800 [thread overview]
Message-ID: <2bd747c7.0302050833.67c479d8@posting.google.com> (raw)
In-Reply-To: Pine.LNX.4.44.0302031943250.16795-100000@heidegger.mousecar.net
gebser@ameritech.net wrote in message news:<Pine.LNX.4.44.0302031943250.16795-100000@heidegger.mousecar.net>...
>
> My first thought was simply to edit my own (local) ".emacs" and putting
> it on his machine (as, say, .emacs-ken, then doing "emacs -t
> .emacs-ken"). I was looking for something even simpler and more
> discrete than that. (Sheesh, I'm a lazy SOB.)
I remember playing around with this. My issue was that
the color changes my .emacs set up wouldn't come into effect
if I manually loaded the .emacs. But this .emacs (on the remote
machine) seemed to work just fine:
(eval-after-load 'dot-emacs
(load-file "/bigfaceworm@localmachine.com:/path/to/bigfaceworm/.emacs"))
(provide 'dot-emacs)
hth,
BFW
next prev parent reply other threads:[~2003-02-05 16:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1346.1044295047.21513.help-gnu-emacs@gnu.org>
2003-02-03 23:45 ` Loading local .emacs from remote machine Kevin Rodgers
2003-02-04 1:08 ` gebser
2003-02-05 16:33 ` bigfaceworm [this message]
2003-02-05 19:09 ` gebser
2003-02-07 22:12 ` Brian Palmer
2003-02-04 6:39 ` Kai Großjohann
2003-02-04 16:35 ` gebser
2003-02-04 17:30 ` Kai Großjohann
2003-02-04 21:51 ` gebser
2003-02-06 7:44 ` Mac
2003-02-06 13:42 ` Kai Großjohann
2003-02-06 14:06 ` Glenn Morris
2003-02-06 15:12 ` Kai Großjohann
2003-02-06 15:42 ` Glenn Morris
[not found] <mailman.1406.1044395706.21513.help-gnu-emacs@gnu.org>
2003-02-04 23:30 ` Kevin Rodgers
2003-02-05 0:38 ` gebser
2003-02-05 0:50 ` David Kastrup
2003-02-05 12:45 ` gebser
2003-02-05 12:37 ` gebser
2003-02-05 12:51 ` Kai Großjohann
2003-02-05 15:17 ` gebser
2003-02-05 16:04 ` David Kastrup
2003-02-05 17:06 ` Kevin Rodgers
2003-02-03 17:56 gebser
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=2bd747c7.0302050833.67c479d8@posting.google.com \
--to=bigfaceworm@hotmail.com \
/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).