all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Custom themes
Date: Sat, 25 Jun 2005 13:00:51 -0500 (CDT)	[thread overview]
Message-ID: <200506251800.j5PI0pa13313@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1DmDhu-0004Gj-7F@fencepost.gnu.org> (rms@gnu.org)

	 But, by experimentation, I was able to figure out
       what it currently actually does: it writes files into random
       directories all over your file system without warning.

   That is a rather vague description of the behavior.
   Perhaps you're describing a bug where it writes
   a file into the wrong directory.  If so, can you fix it?

It writes a file into the current directory, which to me does
definitely not seem like the right thing to do for a command like
`customize-create-theme'.  It should write the file into the directory
where these files belong.  I can not possibly fix it, because I have
no idea what directory that is.  The user's home directory?  I do not know.

Here is a list of problems with `customize-create-theme':

1.  The buffer it creates fails to give anywhere close to appropriate
    usage guidance.

2.  The command does things that for most purposes feel like putting
    the buffer in a given major mode, except that it does not run a
    mode hook, nor `after-change-major-mode-hook'.  For instance, it
    calls `kill-all-local-variables' and `use-local-map'.  But instead
    of actually defining and calling a major mode, it kind of
    "inlines" the call to the unofficial major mode.  The buffer ends
    up "officially" in Fundamental Mode, so you can not get info about
    the "hidden" real mode, using `C-h m'.  Because of the
    `use-local-map' call the buffer does not feel like "Fundamental
    Mode".  Because after-change-major-mode-hook has not been called,
    it is not _really_ in Fundamental Mode.  It is in _no_ major mode.
    That is not good.  It could create problems, for instance for
    minor modes defined with define-global-minor-mode.

3.  If now you click on "Done", a second buffer with the tentative
    theme file appears.  It is marked modified and apparently not
    saved to disk.  I believe it should have been either saved to disk
    in the appropriate place, or there should be some message saying
    that saving the file will save it to the appropriate place (and of
    course, that message should not be a lie).

4.  It is a .el file.  The buffer should be in Emacs Lisp mode, but it
    is in Fundamental mode.

5.  You wonder what to do.  You want to save your file, so you do C-x
    C-s, what else?  But that saves it in the current directory, which
    is still the directory that was current when you called
    `customize-create-theme', which may not be an appropriate place
    for theme files.  If you do not pay attention and continue with
    other work, you may have to run `find' to find the file back.  I
    believe that the second buffer's current directory should be the
    directory for saving theme files (whatever directory that is).

Sincerely,

Luc.

  reply	other threads:[~2005-06-25 18:00 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-25  0:31 Custom themes Richard M. Stallman
2005-06-25  1:27 ` Luc Teirlinck
2005-06-25  1:57   ` Luc Teirlinck
2005-06-25 16:40     ` Richard M. Stallman
2005-06-26  3:19       ` Luc Teirlinck
2005-06-26 15:04         ` Richard M. Stallman
2005-06-28  1:21           ` Luc Teirlinck
2005-06-28  1:42             ` Luc Teirlinck
2005-06-28 18:47               ` Richard M. Stallman
2005-06-28 18:46           ` Luc Teirlinck
2005-06-28 20:09             ` Luc Teirlinck
2005-06-27  9:56         ` Per Abrahamsen
2005-06-28  4:57   ` Stefan Monnier
2005-06-28 14:41     ` Luc Teirlinck
2005-06-29  3:58       ` Richard M. Stallman
2005-06-29  4:28         ` Luc Teirlinck
2005-06-30  5:36         ` David Kastrup
2005-06-30 23:11           ` Luc Teirlinck
2005-07-01 22:44             ` Richard M. Stallman
2005-07-02 12:33             ` Richard M. Stallman
2005-07-04  0:27               ` Luc Teirlinck
2005-06-30 12:53       ` Per Abrahamsen
2005-06-28 14:49     ` Luc Teirlinck
2005-06-28 21:29     ` Richard M. Stallman
2005-06-29  3:17       ` Luc Teirlinck
2005-06-29 20:43         ` Richard M. Stallman
2005-06-30  0:59           ` Luc Teirlinck
2005-06-30  5:32             ` David Kastrup
2005-06-30 15:49             ` Richard M. Stallman
2005-06-30 15:49             ` Richard M. Stallman
2005-06-25  3:25 ` Luc Teirlinck
2005-06-25 16:40   ` Richard M. Stallman
2005-06-25 18:00     ` Luc Teirlinck [this message]
2005-06-25 21:01       ` Frank Schmitt
2005-06-25 21:59         ` Luc Teirlinck
2005-06-25 22:03         ` Luc Teirlinck
2005-06-26  4:46       ` Richard M. Stallman
  -- strict thread matches above, loose matches on Subject: below --
2010-10-11  5:15 Chong Yidong
2010-10-11  7:48 ` Deniz Dogan
2010-10-11 15:34   ` Chong Yidong
2010-10-11 16:09 ` Lars Magne Ingebrigtsen
2010-10-11 17:38   ` Chong Yidong
2010-10-11 21:04 ` Eric Lilja
2010-10-12 14:08   ` Joel James Adamson
2010-10-12 20:25 ` Chong Yidong
2010-10-12 23:40   ` Eric Lilja
2010-10-13  0:04   ` Christoph
2010-10-13  2:15     ` Chong Yidong
2010-10-13 20:06   ` David De La Harpe Golden
2010-10-14  4:23     ` Chong Yidong
2010-10-14  4:58       ` Miles Bader
2010-10-13  0:26 ` Stefan Monnier
2010-10-13  2:14   ` Chong Yidong
2010-10-13 10:20     ` Juanma Barranquero
2010-10-13 15:06       ` CHENG Gao
2010-10-13 16:05       ` Chong Yidong
2010-10-14 15:53         ` Chong Yidong
2010-10-14 16:47           ` Juanma Barranquero
2010-10-16 18:33             ` Chong Yidong
2005-07-29 13:54 Richard M. Stallman
2005-06-17 18:45 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200506251800.j5PI0pa13313@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.