Thanks! This is actually what I love doing, small utilities to help me and others which are not that fancy but get the work done and are compatible with my workflow.

Simple and useful - thanks!

And double check the formatting before you tattoo it on your arm.

OSX 10.9 ships a 'seq'. This particular version was written in 2005 by the NetBSD project, and its provenance is NetBSD 3.0 -> FreeBSD 9.0 -> OSX.

Fwiw, it isn't a GNUism, though GNU's version was the first widely distributed one. A 'seq' appears in some old Research UNIX editions, and also in Plan9, but not in commercial AT&T Unix or in BSD. Instead 'jot' is the traditional BSD utility. Not sure if commercial AT&T Unix (and descendants) had anything similar.

nice and simple! added to my .zshrc :)

Here is a copy-n-paste to your bash prompt:

    function hr { printf '=%.0s' $(seq $COLUMNS); }

You can create an alias in git like this:

vim ~/.gitconfig

    ap = !hr && git add -p # Add this line to your file

I honestly don't know of another way, other than encouraging the user to read the code.

Make a Homebrew version :)

Practical example: http://russianroulette.sh

If I have the option to, yes. Or rather I take much less care to actually read the code when I am installing a package out of the Debian repo's. Otherwise, I at least try to review what the heck that I am installing, especially on my own machine.

Not sure if you replied to the wrong comment by accident, but the person you replied to is agreeing with you, while making a general statement about how they wish more people checked the code they're running between the download and run steps.

Piping curl into the shell is bad because the server can choose to serve malicious content to your curl that it didn't show in the browser.

And to head off objections, Piping curl into the shell does not leave any record on disk, unlike the "download .... ./execute" workflow in which it is trivial and natural to insert "and take a quick peek at it too".

Edit: And in the best case scenario, where the script delivered by curl is perfectly innocent, it is still a bad idea since you are left with no authoritative record of what was done. You could run curl again in the future, but that assumes that the same version is delivered, or that the file is still there at all.

Not sure where you got that impression. In lots of cases, package maintainers are people who use the software and are volunteering their time to bundle it up with the necessary bits to put in a distro repo. The same is true of language-specific repos or homebrew.

This doesn't contradict at all what I said. (See http://idioms.thefreedictionary.com/boil+down+to)

I just built a nodejs version of this, available on npm.

http://www.github.com/jaredsohn/hr

Install it via 'npm -g install hr'.

A benefit of this is you can also use it in your node programs (and clientside JS if you use something like browserify.)

And like any software you install that doesn't run in a sandbox, you should look at the source before running it or have some other reason for trusting it. (I briefly thought about how ironic it would be to have this program do something evil, but decided against it.)

It's never a waste of bandwidth if it prompts one person to do the critical checks and prevents them from being owned.

Nice and useful! Thanks!

Love it. Thanks!

Me too, and it's exactly why I made this script :)

Oh yeah! Definitely! Although, to make this non-unicode compatible, it's better to have a cleaner default like '='.

But if you really want another character by default, you can do this:

    alias hr='hr █'

Love this, thanks!

Hardly cause to fork a project - surely it would make more sense as an option to the original?

should rename it to hrd

Great little script. I tossed it into by bash functions and added a bit of error checking and output formatting: https://github.com/jamestomasino/bash-scripts/blob/master/.f...

Or a colored prompt with a timestamp and hostname, great with a huge scrollback.

PS1='\[\033[1;32m\](\A) <\h> [$PWD \$ \[\033[m\]'

Edit: Using tmux with a 200,000 line scrollback, you can also search scrollback based on the hour in which you ran the command. A search for "(12:" would put you right in the ball park.

I just stuck this in my PS1:

    hr() {
        printf '=%.0s' $(seq $((${COLUMNS} - 20)))
    }

    PS1="${GREY}\d ${RED}\$(hr)${GREY} \t"

It dynamically adjusts to the width of the terminal, and looks like this:

    Mon Feb 10 ======================================== 16:30:30

My complete BASH prompt: https://bitbucket.org/wyatt/dotfiles/src/25cb260a05b68dd81a5...

That's an awesome idea, hold on...

My nodejs version does this. (npm -g install hr).

Hi! I implemented your idea, now you can do that! Thanks for your input!

Sorry, the first doesn't work - I was asking if anyone knew why. The second works in BASH, but it's bashism as you note.

And now it works in the bourne shell!

I'm talking about the IBM set that is most common in western locals, often called extended ASCII or just ASCII (since IBM PC became the standard)

For portability you should also use \033 (the octal code) instead of \e, which is non-standard.

Indeed, printf is shorter. I use it in a similar fashion in my own script [1], which can be made to behave like hr() (haven't tried shells other than bash):

    centered_output '=' ''

[1] https://github.com/ppurka/sh_functions/blob/master/my_bash_f...

I use `clear` but in tmux, the whitespace produced by `clear` disappears, so it's the same as pressing <Enter> :(

I like to use terminal colors so it's red, as well as allowing controlling width, but defaulting to terminal width.

  $ cat ~/bin/br
  #!/bin/sh
  if [ "$1" == "" ] ; then
          COLS=`tput cols`
  elif [ "$1" == "--help" ] ; then
          echo "$0: Prints a red line across the screen. or $0 <##> for a specific width."
          echo "$0:   br ; grep -ir foo *  -- place a marker to see where results begin / end."
          echo "$0:   br 80 ; cat file     -- use to check for overly long lines."
          exit
  else
          COLS=$1
  fi
  LINE=""
  for (( x=0 ; x<$COLS ; x++ ));  do LINE="$LINE-" ; done
  echo -e '\E[47;0m'"\033[1m$LINE\033[0m"

I use clear too, far too often, but with tmux, when you scroll up, you don't get the tons of whitespace that you get with just the terminal :(

I've often wondered if there is a terminal which supported the "jump to previous input" functionality described in the stackexchange question but I've never seen anything better than what is mentioned in the answers. I've heard Plan 9's Rio supported something like this but searching around, I can't see any mention of it.

Huh. From there I discovered http://acko.net/blog/on-termkit/

Previous thread: https://news.ycombinator.com/item?id=2559734

Related terminals: https://news.ycombinator.com/item?id=3227702 https://news.ycombinator.com/item?id=3910649

"What happened to TermKit?" on Reddit with a reply from the author: http://www.reddit.com/r/programming/comments/137kd9/18_month...

I'm thinking we'll need a terminal window that interfaces with bash but has overlays in HTML and other controls for scrollback, etc. Maybe a fork of an existing terminal.

The iTerm2 nightly builds have everything you asked for. See here for info about marks in history: https://code.google.com/p/iterm2/wiki/MarksAndNotes

More info about the general idea of integrating the terminal with the shell, including command history: http://www.iterm2.com/shell_integration.html

I expect FinalTerm will do something along the lines of marks as well, and has introduced some cool ideas with history.

Of course, iTerm2 has has had autocomplete for years.

If you'd like a shinier <hr> in iTerm2, you could use this script:

#!/bin/bash # usage: hr image.png printf '\033]1337;File=inline=1;width='`tput cols`';height=8px;preserveAspectRatio=0:' base64 < $1 printf '\007'

If you like this idea and are stuck in Windows, this does the same thing:

    @set @jScript=1;/*
    @for /f "tokens=1,2" %%w in ('mode con:') do @if "%%w" == "Columns:" set cols=%%x
    @cscript /noLogo /E:jScript  "%~f0" %cols% %1 =
    @Goto :EOF
    */line='';while(line.length<WScript.Arguments(0))line+=WScript.Arguments(1);
    WScript.StdOut.Write(line.substr(0,WScript.Arguments(0)));

Save as hr.cmd and stick it somewhere in your path.

Perl on Windows;

   perl -e "$_=`mode`;/ns:\s+(\d+)/;print '='x$1"

I've long wanted a shell with logical separation of each command/output pair.

I thought control + l was a fairly well known hotkey?

it inserts a terminal worth of line breaks

Fortunately this is what I've used Figlet (http://www.figlet.org) or Toilet (http://caca.zoy.org/wiki/toilet) for:

    $ figlet -- ----------
    
    
     _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
    |_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|

PS1="$(hr -) $PS1"

Beautiful.

Now I need a way to make this happen in SBT too.