From: "andrés ramírez" <rrandresf@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47389@debbugs.gnu.org
Subject: bug#47389: 27.1.91; completion issue on eshell
Date: Wed, 21 Apr 2021 16:05:55 +0000 [thread overview]
Message-ID: <86v98faaho.fsf@gmail.com> (raw)
In-Reply-To: <87lfa87pb1.fsf@gnus.org>
Hi. Lars.
>>>>> "Lars" == Lars Ingebrigtsen <larsi@gnus.org> writes:
Lars> andrés ramírez <rrandresf@gmail.com> writes:
>> No. I was NOT able of reproducing this with 'emacs -Q'.
Lars> The backtrace also seems to indicate that em-cmpl file hasn't been byte-compiled at all.
Lars> Or do you perhaps have a copy of the eshell--complete-commands-list somewhere else, for
Lars> instance in your .emacs file?
Today I was reading the list help-gnu-emacs@gnu.org. And I found this
message:
--8<---------------cut here---------------start------------->8---
https://lists.gnu.org/archive/html/help-gnu-emacs/2021-04/msg00216.html
--8<---------------cut here---------------end--------------->8---
On that message Stefan mentions bug#41423. On
bug#41423 I had been testing Stefan's 'minimalist version of the patch'. So Indeed I have a copy of
the function 'eshell--complete-commands-list' at the end of my 'dot emacs'. So I think this bug
report is a continuation of bug#41423.
IMO. This bug should be marked duplicate.
I am going to reply on bug#41423. Explaining the tiny added change on
Stefan's 'minimalist version of the patch' for fixing bug#47389. Perhaps Stefan would indicate
If the change done is right.
Best Regards
next prev parent reply other threads:[~2021-04-21 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 15:09 bug#47389: 27.1.91; completion issue on eshell Andrés Ramírez
2021-03-26 11:45 ` Lars Ingebrigtsen
2021-03-26 12:04 ` andrés ramírez
2021-03-27 12:29 ` Lars Ingebrigtsen
2021-03-27 12:56 ` andrés ramírez
2021-04-21 16:05 ` andrés ramírez [this message]
2021-04-25 19:03 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v98faaho.fsf@gmail.com \
--to=rrandresf@gmail.com \
--cc=47389@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.