all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: John Hurst <ajh@ajhurst.org>
Cc: 73244@debbugs.gnu.org
Subject: bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41
Date: Wed, 23 Oct 2024 10:15:48 +0200	[thread overview]
Message-ID: <8349256a-caea-48ea-9be7-140d24bf0d79@gmx.at> (raw)
In-Reply-To: <ae4c4452-393b-478b-bd31-d7e7e5a773d1@app.fastmail.com>

 > I've added the buffer outputs that you request in the context below.
 >
 > They don't seem to be that informative?  Have I misinterpreted your instructions?

No.  I gave you silly instructions - emacs -Q ignores the early-init.el
file as well.  So please do the following:

(1) Rename your early-init.el file and your .emacs to something else.

(2) Make an early-init.el file that contains

(setq frame-size-history '(100))
(defun resize-me (frame)
    (set-frame-size frame 42 90))

(3) Run emacs without the -Q option so it reads your early-init.el file
and nothing else.

(4) You should now see the splash screen.  Maximize the frame, switch to
the *scratch* buffer and there do

(progn
     (frame--size-history)
     (switch-to-buffer "*frame-size-history*"))

(5) Copy the contents of the buffer *frame-size-history* so you can post
them here.

(6) In your early-init.el file remove everything but the

(setq frame-size-history '(100))

line.

(7) Start emacs without the -Q option from the terminal window.

(8) Repeat steps (4)-(5).

(9) Re-rename your early-init.el and your .emacs files to what they were
before step (1).  In particular, make sure that your early-init.el just
contains the

(setq byte-compile-warnings '(cl-functions))

line you mentioned earlier.

Thanks and sorry for the inconvenience, martin





  reply	other threads:[~2024-10-23  8:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14  2:42 bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41 John Hurst
2024-09-14  2:45 ` bug#73245: " John Hurst
2024-09-14  7:23   ` Eli Zaretskii
2024-09-14  7:25 ` bug#73244: " Eli Zaretskii
2024-09-21  9:50 ` Eli Zaretskii
2024-09-21  9:58   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-21 11:19     ` Eli Zaretskii
2024-10-05  9:55       ` Eli Zaretskii
2024-10-05 11:05         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 11:48           ` Eli Zaretskii
2024-10-13 21:29             ` John Hurst
2024-10-13 23:33               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-14 13:33                 ` Eli Zaretskii
2024-10-14 15:58                   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                     ` <1c429b02-0407-4f9c-8e94-f012463adb01@app.fastmail.com>
     [not found]                       ` <fa8dff61-d923-4fcc-8e90-c76aeb355095@gmx.at>
     [not found]                         ` <cb955552-3695-4160-9514-625b8426db33@app.fastmail.com>
2024-10-21  8:18                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                         ` <e8252eea-b499-4ce1-8e9d-6e7193ff8fb2@app.fastmail.com>
2024-10-21  8:19                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-22 23:59                             ` John Hurst
2024-10-23  8:15                               ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-26  2:01                                 ` John Hurst
2024-10-26  8:43                                   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27  7:32                                     ` John Hurst
2024-10-27  8:47                                       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=8349256a-caea-48ea-9be7-140d24bf0d79@gmx.at \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73244@debbugs.gnu.org \
    --cc=ajh@ajhurst.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.