From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 16678@debbugs.gnu.org
Subject: bug#16678: 24.3.50; REGRESSION: text selection is broken in Customize edit fields
Date: Fri, 7 Feb 2014 09:35:18 -0800 (PST) [thread overview]
Message-ID: <546218f1-7f8c-471e-8172-36ece48c7341@default> (raw)
In-Reply-To: <<83r47fxska.fsf@gnu.org>>
> If I highlight inside the edit field, everything works as expected.
> That is instead of
>
> Put the cursor before the `[' and hit `C-SPC'
>
> I do Put the cursor ON the `[' and hit `C-SPC'
That is what I meant. I should have said "put _point_ before..."
or "put the cursor on...".
> then I get the expected behavior.
This is very weird. When I try now, I do not see the bug.
Last night it was entirely reproducible, from emacs -Q.
The behavior I saw was that selecting the entire text in the
edit field unhighlighted the selection. IOW, selecting the
last char in the field caused unhighlighting.
No matter how I tried to select all of the text in the field,
selecting the last char made the highlighting disappear.
That was the bug I tried to report. For example, just
double-clicking the `[', which selects the whole text `[next]',
did not highlight the selection (perhaps it highlighted then
unhighlighted it).
The text was in fact selected, as I tested by yanking it.
But the selection was not highlighted if it included the last
char.
> What is the purpose of highlighting outside of the edit field?
To be clear, I never tried to select beyond the last char.
I was only selecting all of the text in the field, _including_
the last char. For example, C-SPC followed by <right>...
until the cursor moved past the last char, to select it.
But as I say, for some reason I cannot repro the bug this
morning. I will keep an eye out, to see if it happens again.
But what is weird is that it was reproducible over and over
last night, but not now.
And I in fact still have an Emacs session (but with my setup,
not from emacs -Q) that shows the bugged behavior now.
I tried poking around, to see if I could discover something
different about that Customize buffer, but I haven't found
anything.
If you have an idea of something to look for, and you let me
know soon (e.g., before I forget and quit the session at some
point or the session crashes), let me know and I'll take a look.
next parent reply other threads:[~2014-02-07 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<6c091fb7-c0fe-41b6-a6bd-d787fc53be1a@default>
[not found] ` <<83r47fxska.fsf@gnu.org>
2014-02-07 17:35 ` Drew Adams [this message]
2014-02-07 18:10 ` bug#16678: 24.3.50; REGRESSION: text selection is broken in Customize edit fields Eli Zaretskii
2015-12-26 13:28 ` Lars Ingebrigtsen
2015-12-26 16:30 ` Drew Adams
[not found] ` <<546218f1-7f8c-471e-8172-36ece48c7341@default>
[not found] ` <<83d2iyyes9.fsf@gnu.org>
2014-02-07 18:50 ` Drew Adams
2014-02-07 3:31 Drew Adams
2014-02-07 7:58 ` 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=546218f1-7f8c-471e-8172-36ece48c7341@default \
--to=drew.adams@oracle.com \
--cc=16678@debbugs.gnu.org \
--cc=eliz@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.
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).