From: Lars Ingebrigtsen <larsi@gnus.org>
To: Bruce <brucelam1982pi@anche.no>
Cc: 55870@debbugs.gnu.org
Subject: bug#55870: GNU Emacs 26.3, Select All(C-x h) does not work
Date: Tue, 12 Jul 2022 14:11:25 +0200 [thread overview]
Message-ID: <875yk2sf82.fsf@gnus.org> (raw)
In-Reply-To: <92253b43-50a1-554e-de66-f31f0c423b1f@anche.no> (Bruce's message of "Mon, 11 Jul 2022 20:08:46 +0800")
(Please keep the debbugs address in the CCs -- otherwise it won't reach
the bug tracker.)
Bruce <brucelam1982pi@anche.no> writes:
> -- This was a month ago -- did you manage to reproduce the issue with
> -- "emacs -Q"?
>
> Thanks for your remind, :-)
>
> I reproduce the issue with "emacs -Q" as described in email title
> 'Re: bug#55870: GNU Emacs 26.3, Select All(C-x h) does not work'
> on 2022-06-12. Here was the content (you can search your mail inbox)
>
> Under Linux Mint 20.2 and Debian 11.3
>
> 1. Using emacs -Q or emacs -mm, editing chinese-book.txt(in attachment)
> 2. (C-x h) to select all, GNU Emacs 26.3 only shows "mark set",
> 3. I use M-w to copy, The memory that Emacs consumes jumps from around
> 80MB to
> 1000MB even 1400MB, then it does not responds to keyboard or mouse.
Can you reproduce the problem in a more recent version of Emacs? 26.3
is several years old.
next prev parent reply other threads:[~2022-07-12 12:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 8:50 bug#55870: GNU Emacs 26.3, Select All(C-x h) does not work Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 14:57 ` Lars Ingebrigtsen
[not found] ` <1fc51cba-c767-2e5f-e0be-6e0f8d7d1df6@anche.no>
2022-06-10 12:44 ` Lars Ingebrigtsen
2022-07-11 11:01 ` Lars Ingebrigtsen
[not found] ` <92253b43-50a1-554e-de66-f31f0c423b1f@anche.no>
2022-07-12 12:11 ` Lars Ingebrigtsen [this message]
2022-07-13 3:01 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 10:56 ` Lars Ingebrigtsen
2022-07-13 11:12 ` Visuwesh
2022-07-13 11:43 ` Eli Zaretskii
2022-07-14 9:50 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 10:02 ` Lars Ingebrigtsen
2022-07-14 10:09 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 10:13 ` Eli Zaretskii
2022-07-15 12:44 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-15 13:03 ` Eli Zaretskii
2022-07-16 0:15 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-16 5:37 ` Eli Zaretskii
2022-07-17 2:38 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 6:37 ` Eli Zaretskii
2022-07-17 7:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 7:51 ` Eli Zaretskii
2022-07-17 8:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 10:08 ` Eli Zaretskii
2022-07-17 11:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 12:49 ` Eli Zaretskii
2022-07-17 13:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 0:27 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 1:01 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 0:24 ` Bruce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 16:16 ` Eli Zaretskii
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=875yk2sf82.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55870@debbugs.gnu.org \
--cc=brucelam1982pi@anche.no \
/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).