From: "José L. Doménech" <j_l_domenech@yahoo.com>
To: martin rudalics <rudalics@gmx.at>
Cc: "José L. Doménech" <j_l_domenech@yahoo.com>, 22827@debbugs.gnu.org
Subject: bug#22827: 25.1.50; enchance request for the *Network Security Manager*
Date: Sat, 27 Feb 2016 22:01:44 +0100 [thread overview]
Message-ID: <86si0d98av.wl-j_l_domenech@yahoo.com> (raw)
In-Reply-To: <56D1E649.90505@gmx.at>
Thanks, I was unaware of the "display-buffer-alist" variable.
Again thanks and sorry for the inconvenience.
On Sat, 27 Feb 2016 19:09:13 +0100,
martin rudalics wrote:
>
> > when the *Network Security Manager* finds a problem a buffer pops up
> > by spliting the frame and, with my combination of emacs display
> > configuration and screen resolution, it is not posible to read all the
> > text that points to the problem found in the connection.
> >
> > My request is to allow read all the warning text that the NSM is
> > trying to show, by enabling an option to not split the frame,
>
> (custom-set-variables
> '(display-buffer-alist
> (quote
> (("*Network Security Manager*" display-buffer-same-window)))))
>
> > or
> > enable scroll from the minibuffer or enable change window from the
> > minibuffer or even add a response option to read all the warning text
> > or whatever you see fit best.
>
> I suppose that all of this should be done indeed, so the plain
> ‘read-multiple-choice’ used here is probably suboptimal.
>
> martin
>
next prev parent reply other threads:[~2016-02-27 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 13:29 bug#22827: 25.1.50; enchance request for the *Network Security Manager* José L. Doménech
2016-02-27 18:09 ` martin rudalics
2016-02-27 21:01 ` José L. Doménech [this message]
2016-02-28 5:28 ` Lars Ingebrigtsen
2016-03-04 14:02 ` Lars Ingebrigtsen
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=86si0d98av.wl-j_l_domenech@yahoo.com \
--to=j_l_domenech@yahoo.com \
--cc=22827@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.