unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Cc: emacs-devel@gnu.org, "Daniel Ortmann" <dortmann@lsil.com>
Subject: Re: Should customizing default-frame-alist change existing frames?
Date: Fri, 01 Mar 2002 11:33:15 +0100	[thread overview]
Message-ID: <20020301112225.9416.LEKTU@terra.es> (raw)
In-Reply-To: <rjr8n4g0us.fsf@ssv2.dina.kvl.dk>


> I can see two solutions:
> 
> 1. Change the doc string to say that existing frames will not be
>    affected by setting default-frame-alist, only new ones. 
> 
> 2. Add a :set method that applies the frame parameters to all existing
>    frames.
 
> What do you think?

Perhaps applying the changes to the current frame and any new ones.

Making a customize change for the frame and not seeing the current frame
"adapt" to the changes would be confusing for beginners. More often than
not, the user is going to customize from inside the frame he's working
on, precisely because he does want to change it.

If a user makes the mistake of customizing from inside a special frame
I'd bet he (assuming is not experienced) is doing some exploring 'round
and he'll be able to understand his error.

OTOH, changing all existing frames could be fragile, I think.

                                                           /L/e/k/t/u


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-03-01 10:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01  8:15 Should customizing default-frame-alist change existing frames? Per Abrahamsen
2002-03-01 10:33 ` Juanma Barranquero [this message]
2002-03-01 18:33   ` Stefan Monnier
2002-03-04  9:18     ` Juanma Barranquero
2002-03-04 21:29       ` Kim F. Storm
2002-03-01 10:57 ` Eli Zaretskii
2002-03-01 11:20 ` Kim F. Storm
2002-03-02 19:50 ` Richard Stallman
2002-03-05  8:42 ` Per Abrahamsen
2002-03-05 21:58   ` Richard Stallman
2002-03-06 11:15     ` Per Abrahamsen
2002-03-08  9:08       ` Richard Stallman

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=20020301112225.9416.LEKTU@terra.es \
    --to=lektu@terra.es \
    --cc=dortmann@lsil.com \
    --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).