[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Code for cond*
From: |
Po Lu |
Subject: |
Re: Code for cond* |
Date: |
Thu, 25 Jan 2024 17:10:12 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Alan Mackenzie <acm@muc.de> writes:
> That's just a way of ensuring it never comes to anything and just gets
> forgotten about. If that is done, it will be impossible to replace any
> of the pcase uses in Emacs with cond*.
My thoughts exactly.
> A better way of doing this would be to create a feature branch, which
> can later be merged into master once its advantages become clear.
The same problems that apply to ELPA also apply to feature branches,
except that feature branches are far more demanding in regard to
maintenance.
Thanks.
- Re: Code for cond*, (continued)
- Re: Code for cond*, Emanuel Berg, 2024/01/25
- Re: Code for cond*, Eli Zaretskii, 2024/01/25
- Re: Code for cond*, Emanuel Berg, 2024/01/25
- Re: Code for cond*, Emanuel Berg, 2024/01/24
- Re: Code for cond*, Alan Mackenzie, 2024/01/24
- Re: Code for cond*, Emanuel Berg, 2024/01/24
- Re: Code for cond*,
Po Lu <=
- Re: Code for cond*, Emanuel Berg, 2024/01/25
- Re: Code for cond*, Po Lu, 2024/01/25
- Re: Code for cond*, Emanuel Berg, 2024/01/25
- Re: Code for cond*, Stefan Kangas, 2024/01/25
Re: Code for cond*, Richard Stallman, 2024/01/19
Re: Code for cond*, Stefan Monnier, 2024/01/23