unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 45376@debbugs.gnu.org
Cc: gliao.tw@pm.me
Subject: bug#45376: 28.0.50; [Feature/Native-Comp] strange `ls` output in eshell loaded from eln
Date: Wed, 23 Dec 2020 15:27:29 +0000	[thread overview]
Message-ID: <xjfzh24mtjy.fsf@sdf.org> (raw)
In-Reply-To: <xjf4kkdnen9.fsf@sdf.org> (Andrea Corallo via's message of "Wed,  23 Dec 2020 07:51:54 +0000")

Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:

> "gliao.tw@pm.me" <gliao.tw@pm.me> writes:
>
>> Hi,
>>
>> I checked the last updated feature/native-comp branch (commit 433ae7b0a5cedbcd7b0a1daf12846e38f00fd111) and identified a strange outputs from eln-compiled eshell.
>>
>> The first attachment shows the `ls` command output under eshell loaded
>> from elc, while the second attachment shows the same command, but much
>> stranger output under eshell loaded from eln.
>>
>> I have tested/complied the last updated code on Linux/x86-64,
>> Linux/aarch64 (Debian Bullseye, GCC 10.2.1) and Windows (Msys2), all
>> the test cases generate the same weird output from `ls` under
>> eln-loaded eshell.
>>
>> This issue does not happen on the code based at or before commit f244c21902
>>
>> Thanks,
>> Kiong-Ge.
>
> Hi Kiong-Ge,
>
> yep, I've merged a lot of stuff into the value/type inference logic so
> this is certanly related.
>
> The offending function is `eshell-ls-find-column-lengths', I'll have a
> look.

Hi Kiong-Ge,

as of ffcd490cb4 is working for me, could you give it a try?

Just remember you might need to clean the eln-cache folder to have
eshell freshly recompiled.

Thanks!

  Andrea





  reply	other threads:[~2020-12-23 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23  1:59 bug#45376: 28.0.50; [Feature/Native-Comp] strange `ls` output in eshell loaded from eln gliao.tw--- via 
2020-12-23  7:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-23 15:27   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-12-23 17:10     ` gliao.tw--- via 
2020-12-23 18:51       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-25  5:59         ` Lars Ingebrigtsen
2020-12-25  8:01           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-23 15:34   ` gliao.tw--- via 

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xjfzh24mtjy.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=45376@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=gliao.tw@pm.me \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).