unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "David Vanderschel" <DJV4@Austin.RR.com>
Subject: New symptom and code
Date: Tue, 06 Jul 2004 10:37:48 GMT	[thread overview]
Message-ID: <0ivGc.18253$T72.289@fe2.texas.rr.com> (raw)
In-Reply-To: SEuGc.19816$W6.13450@fe2.texas.rr.com

I should have mentioned that I am using the minibuffer
primarily so that I can get a temporary multi-line
display.  Otherwise, I could have used message.  I am
not letting the user edit in the minibuffer.  I am
just showing him some data.  The single character he
types is treated by my program as a command, which
then modifies the display.

I just encountered another very weird symptom.  I had
two frames open.  I invoked the function as usual in a
frame with a single window - the only window in which
the function was bound to a key.  Its minibuffer grew
in the manner I had intended.  However, the string
which was supposed to go in the minibuffer wound up in
the minibuffer of the other frame.  This makes no
sense.  There is no concept of multiple minibuffers in
the my code.

Maybe I should just show my current iteration of the
code:

(defun Hube-config-dialogue (msg valid-chars)
"Show (possibly multi-line) MSG in minibuffer; read and return an input char.
Return 0 if input character is not among those in list VALID-CHARS."
  (interactive)
  (save-selected-window
    (select-window (minibuffer-window)) (erase-buffer) (insert msg)
    (let ((auto-save-interval 600) (echo-keystrokes 0) (enlargement 0))
      (while (not (pos-visible-in-window-p)) (enlarge-window 1) (incf
enlargement))
      (let* ((s (read-key-sequence nil)) (c (elt s 0)))
        (erase-buffer) (shrink-window enlargement) (if (member c valid-chars) c
0)))))

What do I need to understand to get this right?

Regards,
  David V.

  reply	other threads:[~2004-07-06 10:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06  9:53 Minibuffer wipeout: "Auto-saving... done" David Vanderschel
2004-07-06 10:37 ` David Vanderschel [this message]
2004-07-06 18:15   ` New symptom and code Kevin Rodgers
2004-07-07  1:16     ` David Vanderschel
2004-07-07  1:24       ` David Kastrup
2004-07-07 16:04       ` Kevin Rodgers
2004-07-08  2:05         ` David Vanderschel
2004-07-06 10:42 ` David Vanderschel
2004-07-10 17:17   ` Kai Grossjohann
2004-07-06 18:13 ` Minibuffer wipeout: "Auto-saving... done" Kevin Rodgers
2004-07-08  2:26   ` David Vanderschel

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='0ivGc.18253$T72.289@fe2.texas.rr.com' \
    --to=djv4@austin.rr.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).