[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-
From: |
Eli Zaretskii |
Subject: |
bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands |
Date: |
Fri, 02 Aug 2019 09:41:37 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 21867@debbugs.gnu.org, zkanfer@gmail.com
> Date: Thu, 01 Aug 2019 21:25:49 +0200
>
> >> C-x C-e ;; eval-last-sexp
> >> a C-h l ;; view-lossage
> >>
> >> which is a very curious way of displaying this. It makes it look like
> >> "a C-h l" is a key stroke.
> >
> > A newline should be enough to fix that, I think.
>
> Yes, that'd be OK, I think, but it means that we have to
> put... something... into the recent_keys variable to mark the "a" as
> having been read by `read-string'. I suggested (nil . "some-string"),
> but perhaps just (nil) would be OK?
Or maybe a special symbol?
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/01
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Eli Zaretskii, 2019/08/01
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/01
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Eli Zaretskii, 2019/08/01
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/01
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Eli Zaretskii, 2019/08/01
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/01
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands,
Eli Zaretskii <=
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/02
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Eli Zaretskii, 2019/08/02
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Stefan Monnier, 2019/08/02
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/03
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Stefan Monnier, 2019/08/03
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/03
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Juri Linkov, 2019/08/03
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Lars Ingebrigtsen, 2019/08/04
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Juri Linkov, 2019/08/04
- bug#21867: 25.0.50; lossage's log doesn't treat characters read by read-char as separate commands, Stefan Monnier, 2019/08/04