emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org, Tommy Kelly <tommy.kelly@verilab.com>
Subject: Re: Re: Minor gotcha with org-agenda-files
Date: Sun, 23 Jan 2011 10:06:45 +0000	[thread overview]
Message-ID: <87lj2clyru.fsf@ucl.ac.uk> (raw)
In-Reply-To: <AANLkTimcZyeZZDPUtNRu=VcoQY215tzLFS=KSRq=i+kv@mail.gmail.com> (suvayu ali's message of "Sun, 23 Jan 2011 09:15:44 +0100")

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> Hi Tommy and Eric,
> On Sat, Jan 22, 2011 at 8:59 PM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>> Tommy Kelly <tommy.kelly@verilab.com> writes:
>>> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>>>> This is nothing org specific. Its how customise works. This is the
>>>> reason people are encouraged to _not_ mix customise with setq. I for
>>>> example use customise for everything except org settings.
>>> Ah but hang on.
>>> First, is it reasonable to consider it obvious (I mean, it wasn't to me)
>>> that using C-c [ invokes customize?
>>> Second, even if it is reasonable, isn't it the case that customize
>>> offers a temporary change of variables? You have to explicitly ask it to
>>> make the change permanent, no?
>> It would indeed be friendlier if this were done here as well.
> I am not familiar with how to interface ui with customize so I don't
> know whether its possible or not, but there are many instances in
> emacs where this is done as standard practice. For example marking
> certain file local variables as safe, or turning on some special
> behaviour when invoked for the first time (e.g. side scrolling).
> However I do recall all of these prompts the user whether they want to
> keep the settings temporary or make it permanent. So I would say its a
> Request for Feature Enhancement / Bug rather than a mere documentation
> bug.

Yes, I think this is the key aspect: all other instances of commands in
Emacs modifying the .emacs file, that I am aware of, indicate they are
about to do so although sometimes in a roundabout kind of way
(e.g. "make this change permanent").

So, can we have a feature request for this?  A simple y-or-n-p type
prompt would suffice.

Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)

  reply	other threads:[~2011-01-23 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 16:31 Minor gotcha with org-agenda-files Tommy Kelly
2011-01-22 16:49 ` suvayu ali
2011-01-22 17:41   ` Tommy Kelly
2011-01-22 19:59     ` Eric S Fraga
2011-01-23  8:15       ` suvayu ali
2011-01-23 10:06         ` Eric S Fraga [this message]
2011-01-23 10:53           ` Carsten Dominik
2011-01-23 13:56             ` Bernt Hansen

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:

  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=87lj2clyru.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    --cc=tommy.kelly@verilab.com \


* 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


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