zsh-users
 help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: Eric Freese <ericdfreese@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Anyone familiar with auto-fu.zsh project?
Date: Wed, 13 Jun 2018 02:26:47 -0500	[thread overview]
Message-ID: <5DD9F0D4-8348-4707-AE6B-1D47AE58FD2D@dana.is> (raw)
In-Reply-To: <CAAikoAJYE=vyLUpwZcG4j85ENxqVVfRqDSFms1dOFUTzx52Pig@mail.gmail.com>

On 12 Jun 2018, at 23:09, Eric Freese <ericdfreese@gmail.com> wrote:
>Is it possible to get the current subshell's pid without having to load the
>zsh/system module ($sysparams param)? Bash seems to have the $BASHPID
>variable. Is there anything like that in zsh core?

I asked about that as well once and sysparams was the only suggestion i got.

On 12 Jun 2018, at 23:09, Eric Freese <ericdfreese@gmail.com> wrote:
>Or, alternatively, is it reasonable to assume that everyone will be able to
>load the zsh/system module? Background here is that I had a user send a
>pull request to zsh-autosuggestions requesting we don't depend on zsh/zpty
>module since some people may not have it installed, so I'm trying to
>minimize dependencies on non-core modules.

I'm pretty sure that was me. And no, you can't assume that users will have
zsh/system. Which modules are available to zsh is up to the packager, but these
are the ones that are linked by default with --disable-dynamic:

zsh/compctl
zsh/complete
zsh/complist
zsh/computil
zsh/datetime
zsh/main
zsh/parameter
zsh/rlimits
zsh/sched
zsh/termcap
zsh/zle
zsh/zleparameter
zsh/zutil

So i think those are essentially the 'core' modules. You can probably include
zsh/langinfo and zsh/terminfo in most cases too. Those are the ones i had on the
system that inspired that PR, anyway.

dana


  reply	other threads:[~2018-06-13  7:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 17:42 Sebastian Gniazdowski
2018-06-06 18:35 ` Eric Freese
2018-06-09 15:30   ` Sebastian Gniazdowski
2018-06-10  0:58     ` Eric Freese
2018-06-11  5:24       ` Sebastian Gniazdowski
2018-06-11  8:25         ` Eric Freese
2018-06-11  9:46           ` Sebastian Gniazdowski
2018-06-12  1:55             ` Eric Freese
2018-06-12 10:23               ` Sebastian Gniazdowski
2018-06-12 11:32               ` Peter Stephenson
2018-06-13  4:09                 ` Eric Freese
2018-06-13  7:26                   ` dana [this message]
2018-06-13  7:32                     ` Sebastian Gniazdowski
2018-06-13  8:28                       ` Sebastian Gniazdowski
2018-06-13  9:17                         ` dana
2018-06-13 10:48                           ` Sebastian Gniazdowski
2018-06-13 11:43                             ` dana
2018-06-14  8:55                           ` Peter Stephenson
2018-06-14  9:48                             ` dana
2018-06-14 10:00                               ` Peter Stephenson
2018-06-13  7:27                   ` Sebastian Gniazdowski
2018-06-06 23:45 ` Takeshi Banse

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=5DD9F0D4-8348-4707-AE6B-1D47AE58FD2D@dana.is \
    --to=dana@dana.is \
    --cc=ericdfreese@gmail.com \
    --cc=zsh-users@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).