GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Julia Evans (b0rk@social.jvns.ca)'s status on Tuesday, 01-Apr-2025 06:15:55 JST Julia Evans Julia Evans

    i can tell I've been writing this terminal zine for too long because I just had the thought "oh, it might be fun to read `man bash`”

    In conversation about 3 months ago from social.jvns.ca permalink
    • Embed this notice
      Garrett Wollman (wollman@mastodon.social)'s status on Tuesday, 01-Apr-2025 06:15:50 JST Garrett Wollman Garrett Wollman
      in reply to
      • R.I.Pienaar

      @ripienaar @b0rk Quoth The Standard:

      If file does not contain a <slash>, the shell shall use the search path specified by PATH to find the directory containing file. Unlike normal command search, however, the file searched for by the dot utility need not be executable. If no readable file is found, a non-interactive shell shall abort; an interactive shell shall write a diagnostic message to standard error, but this condition shall not be considered a syntax error.
      (SUSv7 but unchanged I think.)

      In conversation about 3 months ago permalink
    • Embed this notice
      Garrett Wollman (wollman@mastodon.social)'s status on Tuesday, 01-Apr-2025 06:15:50 JST Garrett Wollman Garrett Wollman
      in reply to
      • R.I.Pienaar

      @ripienaar @b0rk I think bash has always had `source`, which is a csh-ism that was never in the Bourne or Korn shell, and it's always been equivalent to the `.` command going back to pre-1.x days.

      In conversation about 3 months ago permalink
      feld likes this.
    • Embed this notice
      R.I.Pienaar (ripienaar@devco.social)'s status on Tuesday, 01-Apr-2025 06:15:51 JST R.I.Pienaar R.I.Pienaar
      in reply to

      @b0rk damn

      In conversation about 3 months ago permalink
    • Embed this notice
      Julia Evans (b0rk@social.jvns.ca)'s status on Tuesday, 01-Apr-2025 06:15:52 JST Julia Evans Julia Evans
      in reply to
      • R.I.Pienaar

      @ripienaar the man page claims source is just a synonym for `.`

      In conversation about 3 months ago permalink
    • Embed this notice
      R.I.Pienaar (ripienaar@devco.social)'s status on Tuesday, 01-Apr-2025 06:15:53 JST R.I.Pienaar R.I.Pienaar
      in reply to

      @b0rk I seem to recall “. Foo.sh” doesn’t do that?

      In conversation about 3 months ago permalink

      Attachments


    • Embed this notice
      Julia Evans (b0rk@social.jvns.ca)'s status on Tuesday, 01-Apr-2025 06:15:54 JST Julia Evans Julia Evans
      in reply to

      I am learning some upsetting-to-me things from reading the bash man page, for example that in bash `source blah.sh` will by default search all directories in your PATH for a file called `blah.sh`

      In conversation about 3 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: blah.sh
        The Common Web
    • Embed this notice
      Julia Evans (b0rk@social.jvns.ca)'s status on Thursday, 03-Apr-2025 06:23:35 JST Julia Evans Julia Evans
      in reply to
      • Xavier Ashe :donor:

      @Xavier I thought `source blah.sh` was the same as `source ./blah.sh`!

      In conversation about 3 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: blah.sh
        The Common Web
      Haelwenn /элвэн/ :triskell: likes this.
    • Embed this notice
      Xavier Ashe :donor: (xavier@infosec.exchange)'s status on Thursday, 03-Apr-2025 06:23:36 JST Xavier Ashe :donor: Xavier Ashe :donor:
      in reply to

      @b0rk What should be the correct behavior?

      In conversation about 3 months ago permalink
    • Embed this notice
      Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 03-Apr-2025 06:29:40 JST Haelwenn /элвэн/ :triskell: Haelwenn /элвэн/ :triskell:
      in reply to
      • Xavier Ashe :donor:
      • Swiss Army Nerd
      • malte

      @malte @wesmorgan1 @b0rk @Xavier Yeah same there, in fact I'd more except some kind of BASH_PATH if it really wanted to resolve something, quite like there is an LD_LIBRARY_PATH.

      Although well checking POSIX, the similar dot command has the same behavior: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19_19

      So should be the behavior of most shells.

      In conversation about 3 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: pubs.opengroup.org
        Shell Command Language
    • Embed this notice
      Swiss Army Nerd (wesmorgan1@mastodon.social)'s status on Thursday, 03-Apr-2025 06:29:42 JST Swiss Army Nerd Swiss Army Nerd
      in reply to
      • Xavier Ashe :donor:
      • malte

      @malte @b0rk @Xavier

      Since PATH is consulted for all other commands, so why shouldn't it be consulted for scripts?

      In conversation about 3 months ago permalink
    • Embed this notice
      malte (malte@anticapitalist.party)'s status on Thursday, 03-Apr-2025 06:29:42 JST malte malte
      in reply to
      • Xavier Ashe :donor:
      • Swiss Army Nerd

      @wesmorgan1 @b0rk @Xavier but "source" is for sourcing bash-script, which could even be 600 permissionwise, while $PATH contains _executables_ of all sort of flavours?

      In conversation about 3 months ago permalink
    • Embed this notice
      Swiss Army Nerd (wesmorgan1@mastodon.social)'s status on Thursday, 03-Apr-2025 06:29:44 JST Swiss Army Nerd Swiss Army Nerd
      in reply to
      • Xavier Ashe :donor:

      @b0rk @Xavier

      Huh...I, for one, expect PATH to be consulted by default.

      In conversation about 3 months ago permalink
    • Embed this notice
      malte (malte@anticapitalist.party)'s status on Thursday, 03-Apr-2025 06:29:44 JST malte malte
      in reply to
      • Xavier Ashe :donor:
      • Swiss Army Nerd

      @wesmorgan1 @b0rk @Xavier why, though?

      In conversation about 3 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.