From: Colin Baxter <m43cap@yandex.com>
To: help-gnu-emacs@gnu.org
Subject: Re: mode-line icon for encrypted file
Date: Sat, 04 May 2024 19:25:54 +0100 [thread overview]
Message-ID: <87msp5zb65.fsf@yandex.com> (raw)
In-Reply-To: 87cyq1h29x.fsf@yandex.com
>>>>> Colin Baxter <m43cap@yandex.com> writes:
>>>>> Michael Albinus <michael.albinus@gmx.de> writes:
>> Colin Baxter <m43cap@yandex.com> writes: Hi Colin,
>>> I have discovered I can't access that advantage of the icon. If
>>> I launch emacs with -Q then putting the point over the icon and
>>> clicking does indeed display the password en clair. However this
>>> is not the case when I use my ~/.emacs. Then I get the error:
>>>
>>> Debugger entered--Lisp error: (error "Can't expand minibuffer to
>>> full frame") (signal error ("Can't expand minibuffer to full
>>> frame")) (error "Can't expand minibuffer to full frame")
>>>
>>> I don't yet know what is causing this error.
>> I recommend to bisect your .emacs, until you find the guilty
>> setting.
>>> Colin.
>> Best regards, Michael.
> The fault doesn't appear to be with my ~/.emacs. If I launch emacs
> with -Q and load my emacs via M-x load-file <RET> ~/.emacs <RET>
> then there is no "minibuffer to full frame" error and I see the
> password by clicking the icon. If I remove my ~/.emacs altogether
> and have an empty file ~/.emacs then the error reappears when I
> launch emacs normally, without the Q argument.
> I wonder if it is because I am using stumpwm as my window
> manager. I need to switch computers and try with a different
> window manager.
> I will report back!
> Colin.
Success. The fault is indeed with the stumpwm window manager. If I use a
different one, eg openbox, then there is no error and clicking the icon
shows the password. I suppose I ought to post the problem to stumpwm dev.
Thank you for all your help.
Colin.
next prev parent reply other threads:[~2024-05-04 18:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 11:31 mode-line icon for encrypted file Colin Baxter
2024-05-03 11:51 ` Eli Zaretskii
2024-05-03 20:18 ` Colin Baxter
2024-05-04 6:23 ` Eli Zaretskii
2024-05-04 7:00 ` Colin Baxter
2024-05-04 8:06 ` Eli Zaretskii
2024-05-04 9:51 ` Colin Baxter
2024-05-04 16:44 ` Michael Albinus
2024-05-04 18:15 ` Colin Baxter
2024-05-04 18:25 ` Colin Baxter [this message]
2024-05-05 10:43 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-05-05 13:47 ` Colin Baxter
2024-05-05 14:48 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-05 15:36 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-05-05 15:49 ` Colin Baxter
2024-05-06 11:26 ` Michael Heerdegen
2024-05-06 14:23 ` Colin Baxter
2024-05-06 15:24 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-06 19:20 ` Colin Baxter
2024-05-06 20:16 ` Stefan Monnier
2024-05-03 16:06 ` Michael Albinus
2024-05-03 20:24 ` Colin Baxter
2024-05-04 8:05 ` Michael Albinus
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=87msp5zb65.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=help-gnu-emacs@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.
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).