[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#66890: 29.1; buffer-size should also accept the buffer's name as str
From: |
Stefan Kangas |
Subject: |
bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument |
Date: |
Sat, 4 Nov 2023 03:43:26 -0700 |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Maybe we should just "de-emphasize" the fact that those functions also
>>> accept strings, and instead insist that you have to go through
>>> `get-buffer` (or `get-buffer-create`). If that sounds vague and you
>>> don't know what that would mean concretely, well.. you're not alone :-)
>> Perhaps we could recommend against abusing it in `(elisp) Tips'.
>
> It's not as strong a "de-emphasize" as I was picturing, but yes,
> that counts.
Feel free to propose other things we could do. I just proposed the
first one that came to mind. :-)
- bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument, Daniel Nagy, 2023/11/02
- bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument, Eli Zaretskii, 2023/11/02
- bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument, Daniel Nagy, 2023/11/04
- bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument, Drew Adams, 2023/11/04
- bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument, Eli Zaretskii, 2023/11/05
- bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument, Stefan Monnier, 2023/11/05
- Message not available
- bug#66890: 29.1; buffer-size should also accept the buffer's name as string argument, Eli Zaretskii, 2023/11/03