manateelazycat / manateelazycat/multi-term
Compilation warnings with Emacs 30
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 21
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
First of all, thanks for multi-term. I have been using it for many years now.
I just upgraded to Emacs 30, and I got the following compilation warnings. I mean, a Warnings buffer automatically comes up:
⛔ Warning (native-compiler): ~/.emacs.d/elpa/multi-term-20200514.428/multi-term.el:637:6: Warning: the function ‘with-parsed-tramp-file-name’ is not known to be defined.
⛔ Warning (native-compiler): ~/.emacs.d/elpa/multi-term-20200514.428/multi-term.el:636:15: Warning: the function ‘tramp-tramp-file-p’ is not known to be defined.
⛔ Warning (native-compiler): ~/.emacs.d/elpa/multi-term-20200514.428/multi-term.el:522:16: Warning: the function ‘ecb-activate’ is not known to be defined.
⛔ Warning (native-compiler): ~/.emacs.d/elpa/multi-term-20200514.428/multi-term.el:521:16: Warning: the function ‘ecb-deactivate’ is not known to be defined.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with multi-term.el at lines 521-522 and 636-637, where Emacs 30 reports unknown functions. Reproduce the warnings by compiling the package with Emacs 30, then inspect how those functions are referenced. Done means the reported native-compilation warnings no longer appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs-lisp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100