[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#68213: 30.0.50; completion-preview-tests failure in --without-x buil
From: |
Eli Zaretskii |
Subject: |
bug#68213: 30.0.50; completion-preview-tests failure in --without-x build |
Date: |
Mon, 08 Jan 2024 14:48:24 +0200 |
> From: Po Lu <luangruo@yahoo.com>
> Cc: Eshel Yaron <me@eshelyaron.com>, Eli Zaretskii <eliz@gnu.org>,
> jm@pub.pink, 68213@debbugs.gnu.org
> Date: Mon, 08 Jan 2024 14:16:54 +0800
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > But why is `mouse-4` sometimes on `mouse-wheel-down-event` and sometimes
> > on `mouse-wheel-down-alternate-event`? What difference does it make?
> >
> > But, AFAICT the `wheel-up/down` events always mean the same, so I think
> > `mwheel.el` should just always bind `wheel-DIR` events and then the
> > `mouse-wheel-DIR-event` vars are used only for those cases where other
> > events also need to be bound, like in the patch below, WDYT?
>
> I think we should let sleeping dogs lie, because the last time changes
> were made to these options in mwheel.el, several obscure problems
> emerged under text terminals that required another round of changes,
> yielding the current values.
There's one dog we cannot let lie: the one that fails the test in
completion-preview-tests to fail to compile -- this is what started
this bug report, and I would like to solve that problem.
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, (continued)
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Eshel Yaron, 2024/01/03
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Eli Zaretskii, 2024/01/03
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Eshel Yaron, 2024/01/05
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Eli Zaretskii, 2024/01/05
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Stefan Monnier, 2024/01/07
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Eli Zaretskii, 2024/01/07
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Stefan Monnier, 2024/01/07
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Po Lu, 2024/01/07
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Stefan Monnier, 2024/01/07
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Po Lu, 2024/01/08
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build,
Eli Zaretskii <=
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Po Lu, 2024/01/08
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Eli Zaretskii, 2024/01/08
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Stefan Monnier, 2024/01/08
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Stefan Monnier, 2024/01/08
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Po Lu, 2024/01/08
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Stefan Monnier, 2024/01/08
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Stefan Monnier, 2024/01/09
- bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, Drew Adams, 2024/01/09
bug#68213: 30.0.50; completion-preview-tests failure in --without-x build, john muhl, 2024/01/02