bashrc_dispatch

Dev tools

shell configuration

SHOW HN2012

173points
42comments
#102of 1,677 in 2012
Top 7%of 2012 by points

How HN took it

DebatedReal support and real criticism

5 positive, 6 neutral or asking, 0 mixed, 4 critical, out of 15 comments about the project. Thread score +0.15.

Idea: 2 for, 3 againstExecution: 1 for, 0 againstPerformance: 1 for, 0 againstDocs: 1 for, 0 againstDesign: 0 for, 1 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Clean, shareable solution to a confusing problem

    From 3 comments
    • I forked this file into a proper repo [1] and made some adjustments. Now the script does not spawn external processes any longer, making the shell lighter and faster to came up.…
      gioele on HN
    • This is great! I made a little tweak where you can change the locations of the scripts: https://gist.github.com/3323840 I set PREFIX to ~/Dropbox/rcfiles/, and the scripts will…
      bajsejohannes on HN
    • Looks awesome! Please use a github project (also called a repository) for this sort of thing rather than a gist. There isn't a minimum size for a github project's codebase and…
      benatkin on HN
  • Faster shell startup after removing external process spawns

    From 1 comment
    • I forked this file into a proper repo [1] and made some adjustments. Now the script does not spawn external processes any longer, making the shell lighter and faster to came up.…
      gioele on HN

Objections

  • Solution to a problem many engineers do not feel exists

    From 2 comments
    • Solution looking for a problem. Not a particularly good one at that.
      smegel on HN
    • I think most engineers can hack their way to .bashrc even if they don't know the exact differences between those files. And those that can't probably don't need to or can get…
      smegel on HN
  • Breaks the standard bash dotfile convention and relies on symlinks

    From 1 comment
    • I think most engineers can hack their way to .bashrc even if they don't know the exact differences between those files. And those that can't probably don't need to or can get…
      smegel on HN

Requests

  • Move the project to a GitHub repository

    From 1 comment
    • Looks awesome! Please use a github project (also called a repository) for this sort of thing rather than a gist. There isn't a minimum size for a github project's codebase and…
      benatkin on HN
  • Make the script location configurable

    From 1 comment
    • This is great! I made a little tweak where you can change the locations of the scripts: https://gist.github.com/3323840 I set PREFIX to ~/Dropbox/rcfiles/, and the scripts will…
      bajsejohannes on HN

Questions

  • Why bash distinguishes login and interactive shells at all

    From 1 comment
    • Why did someone even decide that the program (the shell executable) needed to behave differently depending on "login" vs. "interactive"? If I'm executing a remote command (e.g.…
      delinka on HN

Alternatives named

  • Spreading logic across the standard bash dotfiles with a guard

    From 2 comments
    • Could you achieve the same outcome by spreading the logic though the three standard bash dotfiles? Standard names plus no symlinks, i could live with that.
      smegel on HN
    • ``` > 'interactive' is when called with -i flag (which sshd does when reached by > ssh with no command passed, i.e if you do 'ssh ls' it should not call > bashrc, but should call…
      drothlis on HN
  • Switching to zsh or another shell

    From 2 comments
    • bash is the problem, the solution to this madness is to not use bash.
      james2vegas on HN
    • Don't other shells have similar issues? ZSH sources .zshenv, .zprofile, .zshrc and .zlogin (and corresponding /etc files) depending on the exact situation. Only difference is…
      masklinn on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/4369485)