From: Eli Zaretskii <eliz@gnu.org>
To: Akshay C <akshaychavan20031@gmail.com>
Cc: 44583-done@debbugs.gnu.org
Subject: bug#44583: 25.3; Emacs aborts with fatal error when a keyboard macro (saved in init.el) is set to run automatically at Emacs startup (Windows 10)
Date: Thu, 12 Nov 2020 20:01:51 +0200 [thread overview]
Message-ID: <83tutuxxm8.fsf@gnu.org> (raw)
In-Reply-To: <CAP3r2sLbsMqab-Obro7sQ23SOEhD2zaL92Mj9uOe92gGwX+BkA@mail.gmail.com> (message from Akshay C on Thu, 12 Nov 2020 23:24:18 +0530)
[Please use Reply All to keep the bug tracker on the CC list.]
> From: Akshay C <akshaychavan20031@gmail.com>
> Date: Thu, 12 Nov 2020 23:24:18 +0530
>
> Thank you for your response. Some text editors allow users to close the editor without saving the buffer to a
> file. The next time they open the editor, the buffer is still open. I wanted to achieve this in Emacs. So I wanted
> Emacs to automatically open "notes" at startup with the remember-notes function, then run recover-this-file
> function to recover any autosave data that I hadn't saved to disk, then enter "yes" at the minibuffer prompt. I
> am not good at elisp, so I recorded a keyboard macro to do the job.
Yes, but when you start Emacs as a daemon, there's no minibuffer to
prompt in, because there's no frame to display.
> I have attached emacs_backtrace.txt to
> this mail.
Thanks. I've fixed the crash for the upcoming Emacs 27.2, in a way
that will use the console to display the messages when there's no
frame.
So I'm therefore closing this bug report.
next prev parent reply other threads:[~2020-11-12 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 18:21 bug#44583: 25.3; Emacs aborts with fatal error when a keyboard macro (saved in init.el) is set to run automatically at Emacs startup (Windows 10) akshaychavan20031
2020-11-11 19:27 ` Eli Zaretskii
2020-11-11 19:36 ` Eli Zaretskii
[not found] ` <CAP3r2sLbsMqab-Obro7sQ23SOEhD2zaL92Mj9uOe92gGwX+BkA@mail.gmail.com>
2020-11-12 18:01 ` Eli Zaretskii [this message]
2020-11-12 17:56 ` bug#44583: Here is the emacs_backtrace.txt Akshay C
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=83tutuxxm8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44583-done@debbugs.gnu.org \
--cc=akshaychavan20031@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).