New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:pad-keys appears to be broken since ae5aba367c3ff83d2457e725781290b6810b4e1a #269
Comments
|
Thanks for the report! So while we are finding issues in each others code, I would like to remind you of this: And while we are at it: (I'm trying to get all the packages I have installed to zero warnings by the end of the year. 😁 ) |
|
Oh, and I almost forgot; why isn't |
That could be solved by putting a
I won't stop using that, because it shouldn't have been marked obsolete in the first place. Of all the forms that shouldn't have been obsoleted, that one is certainly near the top of the list, because of how convenient it is, and how awkward the equivalent code is. When I complained about the mass-obsoleting on the mailing list, I was told to individually justify each one I wanted to not be obsoleted (but it was okay for one developer to en masse mark-as-obsolete forms used in the wild, without discussing it first--and then he virtually disappeared). Who has time for that, but I've at least taken care of one so far: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65555 So I'll file a bug about that when I get around to it. In the meantime, Eli said that obsolescence warnings are the invitation to discussion, not a promise to remove the feature, so the more warnings about that, the better, I guess.
That symbol doesn't even appear in
Good luck with that. It's an eternal game of whack-a-mole. Every new version of Emacs makes new warnings, and solving them on the latest release causes other warnings on older ones. So it's practically impossible to have a package lint and install cleanly on multiple versions.
Because I haven't submitted it yet. And I'm not sure if I want to put it on MELPA or GNU ELPA. |
|
@tarsius Apologies for being curt in my response. I appreciate your bringing issues to my attention. Those in particular just happened to be ones that I've been dealing with for a while. Regarding |
No worries, I didn't take it in a negative way.
Thanks for bringing back
I've submitted joddie/pcre2el#56 for that. Maybe one day I'll also port the advices to "new"advice.
Sure is. But I am winning! Currently I am getting warnings for two out of 107 installed packages. (Often I have to open pull-requests to get those things addressed, and sometimes I even have to maintain local patches (but with
After writing a sentence suggesting one or the other, and then erasing that again, two or three times... no I don't think, I have a strongly held opinion on that. |
The options defined with `taxy-magit-section-define-column-definer' will be put into that group. Suggested-by: Adam Porter <adam@alphapapa.net> magit/transient#269 (comment)
Hi Jonas,
Since I upgraded Transient to 0.5, my makem.el dispatcher seems to be broken. When I run
M-x makem RETI get this backtrace:It appears to me that this was broken in ae5aba3. It seems that the pad-keys value of t is being passed to
truncate-string-to-width, rather than the intended, computed value.Thanks for your work.
The text was updated successfully, but these errors were encountered: