[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help fixing NativeMessaging host: read 32-bit message length in nati
From: |
guest271314 |
Subject: |
Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order |
Date: |
Sat, 24 Jun 2023 20:36:48 -0700 |
Are you suggesting I substitute "shell" for "bash"?
It's not really clear what you are suggesting is problematic with the
source code itself, nor how you would proceed to fix whatever you view is
an issue here.
On Sat, Jun 24, 2023 at 7:57 PM Greg Wooledge <greg@wooledge.org> wrote:
> On Sat, Jun 24, 2023 at 07:26:10PM -0700, guest271314 wrote:
> > > You're aware that dd, head, cat and most other commands are NOT part
> > of bash, right?
> >
> > Yes. "most" is stretching it, though I understand what you are talking
> > about.
>
> It is NOT stretching anything. The overwhelming majority of commands
> available on any realistic system (i.e. not an embedded system or an
> initramfs or a Docker or something) are external, not shell builtins.
>
> On my system, TAB TAB produces this count:
>
> Display all 3363 possibilities? (y or n)
>
> That's over three THOUSAND commands. Out of that set of commands, there
> are 61 shell builtins (as confirmed by "compgen -b | wc") and 22 shell
> keywords ("compgen -A keyword | wc"). I have 11 aliases ("alias | wc"),
> and 16 functions ("compgen -A function | wc").
>
> That means 3253 out of 3363 commands are external. Not part of bash,
> and not part of my personal configuration.
>
> > The system I am on has dd, head, cat exposed in the default shell, Bash.
>
> These are not bash builtins. They are external commands.
>
> unicorn:~$ type head
> head is /usr/bin/head
> unicorn:~$ type dd
> dd is hashed (/usr/bin/dd)
> unicorn:~$ type cat
> cat is hashed (/usr/bin/cat)
> unicorn:~$ type cd
> cd is a shell builtin
>
> You see the difference?
>
>
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, (continued)
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order,
guest271314 <=
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, dan b, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24