[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53242: [PATCH] unify reads from local_var_alist
From: |
Eli Zaretskii |
Subject: |
bug#53242: [PATCH] unify reads from local_var_alist |
Date: |
Fri, 14 Jan 2022 10:08:49 +0200 |
> Date: Fri, 14 Jan 2022 00:23:42 +0000
> From: Sergey Vinokurov <serg.foo@gmail.com>
>
> I've noticed that local_var_alist field of the buffer structure is
> accessed inconsistently. Sometimes it's Fassoc, sometimes it's Fassq and
> other times it's assq_no_quit and even an explicit loop.
>
> I think it's safe to unify all the accesses via assq_no_quit since it's
> an internaly maintained alist that definitely has no cycles and elements
> are cons cells with symbol as their car.
How long can local_var_alist be? This change will not allow the user
to C-g from a long search. Do we care? How about using Fassq
consistently instead?
- bug#53242: [PATCH] unify reads from local_var_alist, Sergey Vinokurov, 2022/01/13
- bug#53242: [PATCH] unify reads from local_var_alist, Lars Ingebrigtsen, 2022/01/14
- bug#53242: [PATCH] unify reads from local_var_alist,
Eli Zaretskii <=
- bug#53242: [PATCH] unify reads from local_var_alist, Lars Ingebrigtsen, 2022/01/14
- bug#53242: [PATCH] unify reads from local_var_alist, Sergey Vinokurov, 2022/01/14
- bug#53242: [PATCH] unify reads from local_var_alist, Eli Zaretskii, 2022/01/14
- bug#53242: [PATCH] unify reads from local_var_alist, Sergey Vinokurov, 2022/01/14
- bug#53242: [PATCH] unify reads from local_var_alist, Eli Zaretskii, 2022/01/15
- bug#53242: [PATCH] unify reads from local_var_alist, Sergey Vinokurov, 2022/01/15
- bug#53242: [PATCH] unify reads from local_var_alist, Corwin Brust, 2022/01/15
- bug#53242: [PATCH] unify reads from local_var_alist, Sergey Vinokurov, 2022/01/15