emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Manish <mailtomanish.sharma@gmail.com>
To: Cameron Horsburgh <cammo@netcall.com.au>
Cc: emacs-orgmode@gnu.org
Subject: Re: Installing on windows
Date: Thu, 5 Feb 2009 13:23:52 +0530	[thread overview]
Message-ID: <e7cdbe30902042353n12f12dfq56634ac2e82b4024@mail.gmail.com> (raw)
In-Reply-To: <20090205061133.GB19921@earth>

On Thu, Feb 5, 2009 at 11:41 AM, Cameron Horsburgh wrote:
[...]
>> >> M-x load-file RET <enter-path-to-.emacs> RET
>> >
>> > Will that unload variables that were previously loaded? I can see this
>> > being an issue, for example, if you've undeclared a variable in .emacs
>> > in order to return to a default value.
>>
>> Yes, this will reset any variables that you might have changed in the
>> session back to the values still defined in .emacs.
>
> Sorry, I wasn't clear. I'm thinking about unsetting variables you have
> in your .emacs to their default values. I just reboot Emacs, but if
> there were a quicker way to revert to a 'pristine' state then load
> .emacs it would be much easier.

I guess a lot depends on what "pristine" means here.

You could have multiple copies of .emacs to achieve various states, I
think but then you will need to define /all/ the variables to their
default values at least in some of those files explicitly so they can be
reset from whatever you have set them to.  A variable not set in .emacs
would stay at it's set value (whether set by another copy of .emacs or
manually.)  In reality I have never needed to so I may not even fully
understand your issue and if any of what I said made sense. :-/

-- 
Manish

  reply	other threads:[~2009-02-05  7:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 17:19 Installing on windows Bill Raynor
2009-02-04 17:47 ` Saurabh Agrawal
2009-02-04 17:48 ` Manish
2009-02-04 18:07   ` Saurabh Agrawal
2009-02-05  2:01     ` Manish
2009-02-05  5:02       ` Saurabh Agrawal
2009-02-05  5:14         ` Manish
2009-02-05  5:18           ` Cameron Horsburgh
2009-02-05  5:30             ` Manish
2009-02-05  6:11               ` Cameron Horsburgh
2009-02-05  7:53                 ` Manish [this message]
2009-02-05  8:25                   ` Cameron Horsburgh
2009-02-06  7:15           ` Saurabh Agrawal
2009-02-06  8:05             ` Manish
2009-02-06 11:26               ` Saurabh Agrawal
     [not found]                 ` <e7cdbe30902060434y5a5011eep1a2567f5facce184@mail.gmail.com>
2009-02-06 13:07                   ` Saurabh Agrawal
2009-02-06 19:52                     ` Manish
2009-02-06 21:24                       ` Chris McMahan
2009-02-06 23:30                         ` Sebastian Rose
2009-02-07  8:20                           ` Manish
2009-02-04 18:16   ` Bill Raynor
2009-02-04 19:52 ` Charles Sebold
2009-02-05  9:38 ` Tony Mc
  -- strict thread matches above, loose matches on Subject: below --
2009-02-06 23:19 Tim O'Callaghan
2009-02-07  9:09 ` Manish

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=e7cdbe30902042353n12f12dfq56634ac2e82b4024@mail.gmail.com \
    --to=mailtomanish.sharma@gmail.com \
    --cc=cammo@netcall.com.au \
    --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).