1. Download Adobe Reader 9.4 from http://get.adobe.com/reader/.  Alternatively, I think you could use this direct link with wget: http://ardownload.adobe.com/pub/adobe/reader/unix/9.x/9.4.0/enu/AdbeRdr9.4-1_i486linux_enu.bin
2. Make the installation binary file executable:
   chmod +x AdbeRdr9.4-1_i486linux_enu.bin
3. Start the installation (as su or sudo):
   sudo ./AdbeRdr9.4-1_i486linux_enu.bin
4. Tell the installer where you want Reader installed.  It suggests /opt, which is a fine place to put it.
5. You're done.  Open a PDF with:
   acroread filename.pdf

No matter how many times I browsed to the correct path, I kept being presented with the exact same dialog box. This was in Windows 7, and the solution was to right-click on the SQL Developer icon and select "Run as administrator". I then used this path: C:\app\shellperson\product\11.1.0\db_1\jdk\jre\bin\java.exe

Turn off the screensaver in X

You can turn off X's screensaver by adding the following code to your .xinitrc:

xset s off

And you can verify that it worked by noting that the timeout is zero with "xset q":

james@tv:~$ xset q
...
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  600
...

Turn off DPMS in X

DPMS (VESA Display Power Management Signaling) is what turns off an idle monitor to save energy. To disable it, add the following to .xinitrc:

xset -dpms

and verify that it worked:

james@tv:~$ xset q
...
DPMS (Energy Star):
  Standby: 1200    Suspend: 1800    Off: 2400
  DPMS is Disabled
...

Screen blanking terminal attributes

This command is almost certainly important, although honestly I don't know the details of it very well. The commands themselves seem pretty obvious, but I've done no research as to whether they are redundant. I've add this to my .xinitrc as well:

setterm -blank 0 -powersave off -powerdown 0

Additional note

While I was trying to figure this stuff out, I came across this command as well, and wanted to at least make note of it:

xset s blank

As far as I can tell, this doesn't control whether the screen will blank, but how it will blank. From the xset man page:

...The blank flag sets the preference to blank the video (if the hardware can do so) rather than display a background pattern, while noblank sets the preference to display a pattern rather than blank the video....

I'm pretty sure that using the "noblank" parameter will cause X's default grey crisscross pattern to display when the screensaver is activated, instead of just blanking the screen.

#!/bin/bash

usage() {
description | fmt -s >&2
}

description() {
cat << HERE

DESCRIPTION
  Upload data and fetch URL from the pastebin http://sprunge.us

USAGE
  $0 filename.txt
  $0 text string
  $0 < filename.txt
  piped_data | $0

NOTES
--------------------------------------------------------------------------
* INPUT METHODS *
$0 can accept piped data, STDIN redirection [<filename.txt], text strings following the command as arguments, or filenames as arguments.  Only one of these methods can be used at a time, so please see the note on precedence.  Also, note that using a pipe or STDIN redirection will treat tabs as spaces, or disregard them entirely (if they appear at the beginning of a line).  So I suggest using a filename as an argument if tabs are important either to the function or readability of the code.

* PRECEDENCE *
STDIN redirection has precedence, then piped input, then a filename as an argument, and finally text strings as an arguments.

  EXAMPLE:
  echo piped | "$0" arguments.txt < stdin_redirection.txt

In this example, the contents of file_as_stdin_redirection.txt would be uploaded. Both the piped_text and the file_as_argument.txt are ignored. If there is piped input and arguments, the arguments will be ignored, and the piped input uploaded.

* FILENAMES *
If a filename is misspelled or doesn't have the necessary path description, it will NOT generate an error, but will instead treat it as a text string and upload it.
--------------------------------------------------------------------------

HERE
exit
}

if [ -t 0 ]; then
  echo Running interactively, checking for arguments... >&2
  if [ "$*" ]; then
    echo Arguments present... >&2
    if [ -f "$*" ]; then
      echo Uploading the contents of "$*"... >&2
      cat "$*"
    else
      echo Uploading the text: \""$*"\"... >&2
      echo "$*"
    fi | curl -F 'sprunge=<-' http://sprunge.us
  else
    echo No arguments found, printing USAGE and exiting. >&2
    usage
  fi
else
  echo Using input from a pipe or STDIN redirection... >&2
  while read -r line ; do
    echo $line
  done | curl -F 'sprunge=<-' http://sprunge.us
fi

So, for example, any of the following commands would work (I cleverly named the script "sprunge" and put it in my $PATH):

ls -lA | sprunge
cat .bashrc | sprunge
sprunge < .bashrc
sprunge .bashrc
sprunge 'if [ -f ~/.bashrc ]; then echo "everything after the word sprunge will be uploaded as a text string"; fi'
## note that the last line needs to be surrounded by single quotes, because of the semicolons.

And here's the short description and usage (which is included above, but maybe more readable here):

DESCRIPTION
  Upload data and fetch URL from the pastebin http://sprunge.us

USAGE
  ./sprunge filename.txt
  ./sprunge text string
  ./sprunge < filename.txt
  piped_data | ./sprunge

NOTES
--------------------------------------------------------------------------
* INPUT METHODS *
./sprunge can accept piped data, STDIN redirection [<filename.txt], text
strings following the command as arguments, or filenames as arguments.
Only one of these methods can be used at a time, so please see the note
on precedence.

* PRECEDENCE *
STDIN redirection has precedence, then piped input, then a filename as
an argument, and finally text strings as an arguments.

  EXAMPLE:
  echo piped | "./sprunge" arguments.txt < stdin_redirection.txt

In this example, the contents of file_as_stdin_redirection.txt would
be uploaded. Both the piped_text and the file_as_argument.txt are
ignored. If there is piped input and arguments, the arguments will be
ignored, and the piped input uploaded.

* FILENAMES *
If a filename is misspelled or doesn't have the necessary path
description, it will NOT generate an error, but will instead treat it
as a text string and upload it.
--------------------------------------------------------------------------

Appropriately, I used the script to upload the script to sprunge. http://sprunge.us/cXjM is the URL, but you can add "?bash" to the end of it to get line numbers and syntax highlighting, like so: http://sprunge.us/cXjM?bash.

dpkg -S /usr/bin/file_i_am_curious_about

Here's an example:

james@tv:~$ dpkg -S /usr/bin/sensible-browser
debianutils: /usr/bin/sensible-browser

This was necessary because I apparently deleted /usr/bin/sensible-browser (which is a script that determines which web browser should be the default). To replace it, I needed to know the original package name, which turned out to be debianutils. From there it was a simple matter to do:

sudo apt-get install --reinstall debianutils

sudo update-alternatives --config editor

This will let you select one of your installed text editors from a list that will look something like this:

There are 5 alternatives which provide `editor'.

  Selection    Alternative
-----------------------------------------------
          1    /bin/ed
 +        2    /bin/nano
          3    /usr/bin/vim.tiny
          4    /usr/bin/mcedit-debian
*         5    /usr/bin/vim.basic

Press enter to keep the default[*], or type selection number:

The "+" indicates the editor that would be selected if Debian had to choose, the "*" indicates your current choice.

Debian also maintains symlinks for sensible-browser and sensible-pager. You can change those easily as well:

sudo update-alternatives --config x-www-browser
sudo update-alternatives --config pager

If you find that your favorite program is not included in the list (most likely because it wasn't installed from a .deb package), you can add it like so:

sudo update-alternatives --install x-www-browser x-www-browser /usr/local/src/firefox/firefox 900

In English, this means install into the category x-www-browser, using the symlink named x-www-browser (found in /etc/alternatives), which points to the binary at /usr/local/src/firefox/firefox, and give it a numerical priority of 900. The priority determines which program Debian would select if set to auto. The largest number wins. This is how I added firefox into the list of potential sensible-browser selections.

Like usual, there are almost certainly specific GNOME or KDE tools to accomplish this goal. Since I'm not running those, however, I'll stick to tools available in almost any X.Org environment (I happen to be using Ratpoison).

First, some terminology. A scancode is the lowest level of identification for a key. If your key doesn't have a scancode, you're out of luck - the kernel doesn't recognize the key at all. A keycode is the next level of identification. If your key's scancode is identified with a keycode, then there's just one more step to make it do what you want. The last level of identification is a symbol. A scancode is mapped to a keycode, which is mapped to a symbol (for example, the letter "e" or "Caps Lock").

Keycodes

Starting out, none of my hotkeys were mapped to symbols, some were mapped to keycodes, and some only had scancodes (thankfully there were no completely "dead" keys). You can check if a key has a keycode by using xbindkeys. In a terminal (in X - not a console) type

xbindkeys -k

followed by the key you want to check. Here's an example of the output from my "Back" hotkey (before I bound it using xbindkeys, but after I assigned a keycode to the scancode, as described at the end of this post):

james@tv:~$ xbindkeys -k
Press combination of keys or/and click under the window.
You can use one of the two lines after "NoCommand"
in $HOME/.xbindkeysrc to bind a key.
"(Scheme function)"
    m:0x10 + c:211
    Mod2 + NoSymbol

Binding keycodes to actions

Using the output from xbindkeys -k, it's easy to bind a key to an action. This will be configured in the ~/.xbindkeysrc file (you may need to create it). It will take effect when you run xbindkeys. You'll probably want to call it in your ~/.xinitrc file. Here's an example of the format from my .xbindkeysrc:

# internet key
"firefox"
  m:0x10 + c:178

# play/pause key
"mpc toggle"
  m:0x10 + c:162

# stop key
"mpc stop"
  m:0x10 + c:164

# previous track key
"mpc prev"
  m:0x10 + c:144

# next track key
"mpc next"
  m:0x10 + c:153

# volume up key
"amixer set 'Headphone' 1%+ ; amixer set 'PCM' 1%+"
  m:0x10 + c:176

# volume down key
"amixer set 'Headphone' 1%- ; amixer set 'PCM' 1%-"
  m:0x10 + c:174

# mute key
"amixer set 'Headphone' toggle ; amixer set 'PCM' toggle"
  m:0x10 + c:160

It's a pretty simple format. Obviously the "#" precedes a comment (and is optional, but recommended). The next line is the command you want the hotkey to run (surrounded by quotes). You'll recognize the final line from the output of xbindkeys -k. I'm not sure if you can use either output line (or both) but mine works fine with just the first line following the "(Scheme function)" line.

That's all there is to it... unless your key does not have a keycode.

Mapping scancodes to keycodes

If xbindkeys -k does not recognize your key, it's probably not associated with a keycode. You can check if the key has a scancode (in other words, if the kernel recognizes the key) by pressing the key and then checking dmesg to see if the key was mentioned. Here's an example of what it will look like (from pushing my "Back" hotkey, before I assigned it to a keycode):

james@tv:~$ dmesg | tail -4
[   48.274918] atkbd.c: Unknown key pressed (translated set 2, code 0x83 on isa0060/serio0).
[   48.274918] atkbd.c: Use 'setkeycodes e003 <keycode>' to make it known.
[   48.789832] atkbd.c: Unknown key released (translated set 2, code 0x83 on isa0060/serio0).
[   48.789832] atkbd.c: Use 'setkeycodes e003 <keycode>' to make it known.

If you get similar output, you're key has a scancode (and is not mapped to a keycode). You can use setkeycodes to assign a keycode to the key. Before doing this, however, you're going to want to make sure that you don't assign it to a keycode that's already in use. You can find this out by looking at your keymap.

james@tv:~$ cp /etc/console/boottime.kmap.gz .
james@tv:~$ gunzip boottime.kmap.gz
james@tv:~$ less boottime.kmap

-- SNIP --

keycode  81 = KP_3
        altgr   keycode  81 = Hex_3
        alt     keycode  81 = Ascii_3
keycode  82 = KP_0
        altgr   keycode  82 = Hex_0
        alt     keycode  82 = Ascii_0
keycode  83 = KP_Period
        altgr   control keycode  83 = Boot
        control alt     keycode  83 = Boot
keycode  84 = Last_Console
keycode  85 =
keycode  86 = less             greater          bar
        alt     keycode  86 = Meta_less
        shift   alt     keycode  86 = Meta_greater
keycode  87 = F11              F23              Console_23       F35
        alt     keycode  87 = Console_11
        control alt     keycode  87 = Console_11
keycode  88 = F12              F24              Console_24       F36
        alt     keycode  88 = Console_12
        control alt     keycode  88 = Console_12
keycode  89 =
keycode  90 =
keycode  91 =
keycode  92 =
keycode  93 =
keycode  94 =
keycode  95 =
keycode  96 = KP_Enter
        altgr   keycode  96 = Hex_F
keycode  97 = Control
keycode  98 = KP_Divide
        altgr   keycode  98 = Hex_B
keycode  99 = Control_backslash
        alt     keycode  99 = Meta_Control_backslash
        shift   alt     keycode  99 = Meta_Control_backslash
        control alt     keycode  99 = Meta_Control_backslash
keycode 100 = AltGr
keycode 101 = Break
keycode 102 = Find            

-- SNIP --

You can see that some keycodes are not being used (89-95, for example), so those are safe to use. (By the way, I've heard that you're supposed to pick a keycode between 1-127, but I don't know why, or what happens if you don't - I've never used one outside of that range).

You can then assign a scancode to one of these unused keycodes using setkeycodes (as root).

setkeycodes 0x83 89

The above code assigns the scancode from my "Back" hotkey to the unused keycode "89". Once that's been done, you can use xbindkeys -k (as described above) to get the correct identifier to bind the key using xbindkeys.

Assuming you want to use this binding after you reboot, you'll want to add the setkeycodes command to /etc/rc.local. Here's an example of mine:

james@tv:~$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

## James added to map the "back", "shopping cart", and "?" keys on Gateway keyboard
setkeycodes 0x83 89 &
setkeycodes 0x81 90 &
setkeycodes 0x82 91 &

exit 0

Please feel free to mention better or alternate ways, or anything that I've got wrong.

The games are:

• World of Goo
• Aquaria
• Gish
• Lugaru
• Penumbra: overture

You can buy the bundle here: http://www.wolfire.com/humble

First, get the package

Go to http://www.google.com/chrome/eula.html and select the 32-bit .deb for Debian/Ubuntu, then click "Accept and Install". This will download google-chrome-beta_current_i386.deb.

Optional: Prevent Chrome from adding the Google repository

If you want Chrome to keep itself up-to-date, don't do this step. However, if you just want to check Chrome out without changing too much, you might want to type the following command at the command line:

sudo touch /etc/default/google-chrome

Install with DPKG

In the directory where you downloaded Chrome:

sudo dpkg --install google-chrome-beta_current_i386.deb

In my case, I didn't have the necessary dependencies, so I got the following errors:

james@tv:~$ sudo dpkg --install google-chrome-beta_current_i386.deb
Selecting previously deselected package google-chrome-beta.
(Reading database ... 24475 files and directories currently installed.)
Unpacking google-chrome-beta (from google-chrome-beta_current_i386.deb) ...
dpkg: dependency problems prevent configuration of google-chrome-beta:
 google-chrome-beta depends on libgconf2-4; however:
  Package libgconf2-4 is not installed.
 google-chrome-beta depends on libxslt1.1; however:
  Package libxslt1.1 is not installed.
 google-chrome-beta depends on libxss1; however:
  Package libxss1 is not installed.
 google-chrome-beta depends on xdg-utils (>= 1.0.1); however:
  Package xdg-utils is not installed.
dpkg: error processing google-chrome-beta (--install):
 dependency problems - leaving unconfigured
Processing triggers for menu ...
Processing triggers for man-db ...
Errors were encountered while processing:
 google-chrome-beta

You can fix that with apt-get, like so:

sudo apt-get -f install

This will grab all of the dependencies Chrome needs. Here's the output (you'll need to type "y" when prompted):

james@tv:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  gconf2-common libgconf2-4 libidl0 liborbit2 libxslt1.1 libxss1 shared-mime-info xdg-utils
Suggested packages:
  desktop-file-utils libgnome2-0 exo-utils libgnomevfs2-bin kdelibs4c2a konqueror
The following NEW packages will be installed:
  gconf2-common libgconf2-4 libidl0 liborbit2 libxslt1.1 libxss1 shared-mime-info xdg-utils
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 3047kB of archives.
After this operation, 11.1MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://ftp.us.debian.org lenny/main gconf2-common 2.22.0-1 [1532kB]
Get:2 http://ftp.us.debian.org lenny/main libidl0 0.8.10-0.1 [87.6kB]
Get:3 http://ftp.us.debian.org lenny/main liborbit2 1:2.14.13-0.1 [249kB]
Get:4 http://ftp.us.debian.org lenny/main libgconf2-4 2.22.0-1 [242kB]
Get:5 http://ftp.us.debian.org lenny/main libxslt1.1 1.1.24-2 [227kB]
Get:6 http://ftp.us.debian.org lenny/main libxss1 1:1.1.3-1 [11.9kB]
Get:7 http://ftp.us.debian.org lenny/main xdg-utils 1.0.2-6.1 [54.3kB]
Get:8 http://ftp.us.debian.org lenny/main shared-mime-info 0.30-2 [644kB]
Fetched 3047kB in 7s (433kB/s)
Selecting previously deselected package gconf2-common.
(Reading database ... 24798 files and directories currently installed.)
Unpacking gconf2-common (from .../gconf2-common_2.22.0-1_all.deb) ...
Selecting previously deselected package libidl0.
Unpacking libidl0 (from .../libidl0_0.8.10-0.1_i386.deb) ...
Selecting previously deselected package liborbit2.
Unpacking liborbit2 (from .../liborbit2_1%3a2.14.13-0.1_i386.deb) ...
Selecting previously deselected package libgconf2-4.
Unpacking libgconf2-4 (from .../libgconf2-4_2.22.0-1_i386.deb) ...
Selecting previously deselected package libxslt1.1.
Unpacking libxslt1.1 (from .../libxslt1.1_1.1.24-2_i386.deb) ...
Selecting previously deselected package libxss1.
Unpacking libxss1 (from .../libxss1_1%3a1.1.3-1_i386.deb) ...
Selecting previously deselected package xdg-utils.
Unpacking xdg-utils (from .../xdg-utils_1.0.2-6.1_all.deb) ...
Selecting previously deselected package shared-mime-info.
Unpacking shared-mime-info (from .../shared-mime-info_0.30-2_i386.deb) ...
Processing triggers for man-db ...
Setting up gconf2-common (2.22.0-1) ...

Creating config file /etc/gconf/2/path with new version
Setting up libidl0 (0.8.10-0.1) ...
Setting up liborbit2 (1:2.14.13-0.1) ...
Setting up libgconf2-4 (2.22.0-1) ...
Setting up libxslt1.1 (1.1.24-2) ...
Setting up libxss1 (1:1.1.3-1) ...
Setting up xdg-utils (1.0.2-6.1) ...
Setting up google-chrome-beta (5.0.375.29-r46008) ...
Setting up shared-mime-info (0.30-2) ...
Processing triggers for menu ...

Now, I'm not sure if this last step is actually necessary, but I figured it couldn't hurt to repeat the original dpkg command, just to make sure it works with no errors (again, in the directory where you downloaded the .deb):

sudo dpkg --install google-chrome-beta_current_i386.deb

This time it worked fine:

james@tv:~$ sudo dpkg --install google-chrome-beta_current_i386.deb
(Reading database ... 25041 files and directories currently installed.)
Preparing to replace google-chrome-beta 5.0.375.29-r46008 (using google-chrome-beta_current_i386.deb) ...
Unpacking replacement google-chrome-beta ...
Setting up google-chrome-beta (5.0.375.29-r46008) ...
Processing triggers for menu ...
Processing triggers for man-db ...

Launch Chrome

google-chrome

This title of this post is not entirely accurate. The post is actually about a script that will list files and directories in the same format as ls -l (the "long listing" format of the ls command), except it will correctly report the size of directories (and all of the files within them). Technically, it is actually in the format of ls -lhL.

This is functionally very different than the output of ls. Typically ls lists the size of directories not including their contents. This produces a very small number, which is the amount of disk space the directory's meta-data takes up (i.e. the names of files within the directory). Here is an example:

ls -lhL

total 116K
drwxr-x--- 1 james users  44K 2010-04-22 17:21 movies
drwxr-x--- 1 james users  48K 2010-04-03 22:22 music
drwxr-x--- 1 james users    0 2009-12-11 16:20 photos
drwxr-x--- 1 james users 4.0K 2009-12-13 22:36 data
drwxr-x--- 1 james users  20K 2010-04-27 00:56 tv

And here is an example of the output of the script (note the size of the directories):

drwxr-x--- 1 james users 178G 2010-04-22 17:21 movies
drwxr-x--- 1 james users  26G 2010-04-03 22:22 music
drwxr-x--- 1 james users 9.9G 2009-12-11 16:20 photos
drwxr-x--- 1 james users  27G 2009-12-13 22:36 data
drwxr-x--- 1 james users 135G 2010-04-27 00:56 tv

That's a pretty big difference. Note that if all you're interested in is the permissions, modification time, and filename, using ls -lh is a much better choice - it's extremely fast and gives you all the information you need. However, if you want to know how much space the contents of each directory is using, you should use the following script:

#!/bin/bash
# script to display the sizes of files and directories in the format of ls -lhL
## note that large space on line 9 (the '	' that follows "cut -d") is a tab, created in a terminal with CTRL+v then TAB
for x in *;
  do
    y="$(echo "$x" | sed -e 's/\[/\\[/g' -e 's/]/\\]/g')"
    echo -e \
      "$(ls -lL | grep "[0-9]\{2\}:[0-9]\{2\} $y$" | sed 's/[ ][ ]*/ /g' | cut -d ' ' -f 1-4) \
        $(du -sh "$x" | cut -d '	' -f 1)" \
      "$(ls -lL | grep "[0-9]\{2\}:[0-9]\{2\} $y$" | sed 's/[ ][ ]*/ /g' | cut -d ' ' -f 6-20 )";
  done \
| column -t \
| sed -e 's/[ ]\([ ][ ]*\)/\1/g' \
| sed -e 's/[ ][ ]*/ /8g' \
| sed 's/\([ ][ ]*\)\([^ ]*\)\([ ]\)\([ ]*\)\([^ ]*[ ]*[^ ]*[ ]*\)\([^ ]*\)\([ ]\)\([ ]*\)/\1\4\2\3\5\8\6\7/'

NOTE - The script is not displayed entirely correctly in this post; on line 8, the multiple spaces in single-quotes (following cut -d) should be a TAB. Although it's displayed incorrectly on the page, if you use either the "view source" or "copy to clipboard" buttons (top-right of the script when you hover over it), it will use the correct character. You can also produce this character in a terminal with CTRL+v followed by TAB.

This script should be named something convenient and saved somewhere in your $PATH. I call the script lsd and save it in "/home/james/bin".

How the script works

If you're the kind of person who likes to know what a script does before copying it from the internet and running it, here's what's going on in this script. Paragraphs are labeled by the script's line numbers.

Lines 4-11. This is a for loop that is run on every (non-hidden) file in your current directory (*). $x is the variable that holds one of the directory's filenames per iteration.

Line 6. $y is a variable that equals $x, except brackets ("[" and "]") are replaced by escaped brackets ("\[" and "\]"), in order to avoid conflict with grep's regular expressions matching.

Lines 7-10. These lines are all part of a long echo command which arranges the data in the same format as ls -lhL. It is echoing three separate command substitution variables, separated by spaces.

Line 8. The first of three command substitutions. Gets a long directory listing, greps out the single line that matches $x, removes extra spaces between sections, and then chops off the 2nd part of the line at the point where the directory size will be displayed.

Line 9. The second of three command substitutions. Gets the size of $x using du -sh and then chops off the end of the line, leaving only the size.

Line 10. The third of three command substitutions. Gets a long directory listing, greps out the single line that matches $x, removes extra spaces between sections, and then chops off the 1st part of the line up to the point after where the directory size will be displayed. Script lines 8, 9, and 10 will form a single line of output for each iteration of the for loop.

Lines 12-15. Each of these lines formats the script's output to match the style of ls -lhL.

Line 12. Sorts the output into columns using column -t.

Line 13. Removes extra spaces according to the following rule: for every group of 2 or more consecutive spaces, subtract one space from that group.

Line 14. Removes extra spaces from the last part of the lines, ensuring that filenames containing spaces do not have multiple consecutive spaces.

Line 15. Swaps certain groups of spaces around in order to match the justification style of ls -lhL. Specifically, user and group names are justified left, while file sizes are justified right.

Please leave a comment if you've tried this script and found any bugs in it.