Skip to content
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

[mu4e bug] wrong-number-of-arguments in mu4e--prepare-draft-buffer #2701

Closed
robstewart57 opened this issue Apr 30, 2024 · 3 comments
Closed
Labels
bug mu4e specific for mu4e new

Comments

@robstewart57
Copy link
Contributor

robstewart57 commented Apr 30, 2024

Describe the bug

Using mu at commit 14a882f , attempt to reply or reply-to-all. This message is printed:

mu4e--fcc-path: Wrong number of arguments: #<subr delete>, 0

How to Reproduce

Here's the backtrace:

Debugger entered--Lisp error: (wrong-number-of-arguments #f(compiled-function (elt seq) "Delete members of SEQ which are `equal' to ELT, and return the result.\nSEQ must be a sequence (i.e. a list, a vector, or a string).\nThe return value is a sequence of the same type.\n\nIf SEQ is a list, this behaves like `delq', except that it compares\nwith `equal' instead of `eq'.  In particular, it may remove elements\nby altering the list structure.\n\nIf SEQ is not a list, deletion is never performed destructively;\ninstead this function creates and returns a new vector or string.\n\nWrite `(setq foo (delete element foo))' to be sure of correctly\nchanging the value of a sequence `foo'.  See also `remove', which\ndoes not modify the argument." #<bytecode 0x13d36d3ec075>) 0)
  delete()
  mu4e--fcc-path(...)
  mu4e--prepare-draft-buffer(...)
  mu4e--draft(reply ...)
  mu4e--draft-with-parent(reply ...)
  mu4e-compose-reply-to(nil t)
  mu4e-compose-wide-reply()
  funcall-interactively(mu4e-compose-wide-reply)
  command-execute(mu4e-compose-wide-reply)

Environment

mu version 14a882f .

GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.18.0, Xaw scroll bars) of 2024-03-07

@robstewart57 robstewart57 added bug mu4e specific for mu4e new labels Apr 30, 2024
@theophilusx
Copy link

theophilusx commented Apr 30, 2024 via email

@djcb djcb closed this as completed in c56f8e2 Apr 30, 2024
@robstewart57
Copy link
Contributor Author

@djcb I can confirm that this fixed the issue.

@djcb
Copy link
Owner

djcb commented Apr 30, 2024

Thanks, @robstewart57!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mu4e specific for mu4e new
Projects
None yet
Development

No branches or pull requests

3 participants