From: Reid Rivenburgh <reid@lanl.gov>
Subject: Re: Multiple frame problem
Date: 04 May 2000 14:38:30 -0600 [thread overview]
Message-ID: <vetr9biqce1.fsf@toespaz.c3.lanl.gov> (raw)
In-Reply-To: dsg@mitre.org's message of "01 May 2000 15:49:14 -0400"
David S Goldberg writes:
> Here's my solution which works with XEmacs. Not sure about Emacs.
> In my .gnus I have:
> (defvar dsg-gnus-edit-buffer "*gnusedit*" "place holder for gnus
> editing")
> (defun dsg-gnus-buffer-predicate (arg)
(string= (buffer-name arg) dsg-gnus-edit-buffer))
> [...]
> (gnus-add-configuration
'(message
(frame 1.0
> (if (not (buffer-live-p gnus-summary-buffer))
> (car (cdr (assoc 'group gnus-buffer-configuration)))
> (car (cdr (assoc 'summary gnus-buffer-configuration))))
> (vertical (user-position t top 1 left 1 name "Gnus Edit"
> buffer-predicate
> dsg-gnus-buffer-predicate)
> (message 1.0 point)))))
> What this says is that when I kill or bury whatever is being put in
> the frame called "Gnus Edit", the buffer it will return to is
> called "*gnusedit*" which is not used for anything else, and
> therefore won't likely show up in any other frame. You can use
> this as the buffer to find and lower. Note that you're better off
> with something like this to do the lowering:
> (lower-frame (window-frame (get-buffer-window "*gnusedit*" t)))
Thanks again for your help, Dave. Do you by any chance create the
*gnusedit* buffer beforehand? I'm using your code, and when I finish
composing something, it returns to the *scratch* buffer, not one
called *gnusedit* (which doesn't exist).
Everything is working pretty well now otherwise, though the lowering
occasionally crashes XEmacs (21.1.9). I haven't looked into that
yet....
Thanks again,
Reid
next prev parent reply other threads:[~2000-05-04 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-26 19:54 Reid Rivenburgh
2000-04-26 20:47 ` Kai Großjohann
2000-04-26 21:00 ` Reid Rivenburgh
2000-05-01 19:49 ` David S. Goldberg
2000-05-04 20:38 ` Reid Rivenburgh [this message]
2000-05-05 17:07 ` David S. Goldberg
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=vetr9biqce1.fsf@toespaz.c3.lanl.gov \
--to=reid@lanl.gov \
/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.
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 NNTP newsgroup(s).