From: Juanma Barranquero <lektu@terra.es>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: ielm working buffer on the modeline
Date: Thu, 28 Feb 2002 15:38:08 +0100 [thread overview]
Message-ID: <20020228152835.6D0D.LEKTU@terra.es> (raw)
In-Reply-To: <5x1yf53hnr.fsf@kfs2.cua.dk>
> I don't see why that kind of buffer is more strange that against
> any other type of buffer.
Well, its not usual for me to test elisp against a mail buffer, but
you're right, the usage pattern is obvioulsy very subjective.
> What I don't understad (but maybe you can enlighten me) is why running
> ielm _on_ test.el is necessary when _developing_ test.el ? What are
> the advantages of doing that?
That depends, I supose, on the way you usually work. I like to minimize
buffer switching and number of windows. Yesterday I was trying (once
again) to develop a jit-lock based lazy line-numbering module, and I
tested changes against the source file in order not to have to switch
back and forth between buffers. Line-numbering is usually non-destructive
wrt the target buffer :)
> And I don't see what buffer-local settings of test.el are interesting
> when developing test.el (unless you are looking into a problem with
> Emacs-Lisp mode).
Perhaps I do that kind of thing often. Before that I developed a
derivative of elisp-mode intended to edit my own .emacs file :)
> What about changing the buffer name rather than the mode-line-process, ie.
<snip>
> At least, that would display the information in the part of the mode line
> where (potentially long) names are already shown.
Ok, I think that's a good idea, but it requires more code, because
ELISP> (setq mode-name '("IELM on " (:eval (buffer-name ielm-working-buffer))))
*** Eval error *** error: "Only strings should be stored in the buffer-local variable mode-name"
/L/e/k/t/u
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-28 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 9:02 ielm working buffer on the modeline Juanma Barranquero
2002-02-28 4:07 ` Richard Stallman
2002-02-28 8:26 ` Juanma Barranquero
2002-02-28 10:27 ` Andreas Schwab
2002-02-28 11:37 ` Juanma Barranquero
2002-02-28 12:38 ` Kim F. Storm
2002-02-28 14:38 ` Juanma Barranquero [this message]
2002-02-28 21:06 ` Kim F. Storm
2002-03-01 8:03 ` Juanma Barranquero
2002-03-01 1:15 ` Stefan Monnier
2002-03-01 8:06 ` Juanma Barranquero
2002-03-01 1:11 ` Richard Stallman
2002-03-01 17:54 ` Kim F. Storm
2002-03-01 1:00 ` Stefan Monnier
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=20020228152835.6D0D.LEKTU@terra.es \
--to=lektu@terra.es \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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.