Sent 20Aug06 from yojuancho to vshnu
+---------- [vshnu] help with vshnu colors, please... ----------
| I'm running vshnu but without colors.
| my console an xterms got colors. ...
| any idea why I cannot see vshnu with full colors?
Hi, I'm guessing that your TERM is set to a terminal type that doesn't
claim to support colors. What do see running at the shell?:
echo $TERM
If it's just 'xterm', you might need to set it to 'xterm-color',
'color_xterm' or something like that. Check your termcap file for
what's available to you. The entry should include "Co#8" or similar
in it for vshnu to automatically recognize that this is a terminal that
supports color.
Alternately, you can manually set $color in vshnu, say by typing
";;$color=1<Return>", then reload the vshnucfg file by typing "^Qc".
-sbk

I'm running vshnu but without colors.
my console an xterms got colors.
also run the termcolors script, showing all of the colors my *terms
can reproduce.
this is my vshnu -V output:

                 perl 5.8.7 i486-linux
        Sys::Hostname 1.11
         Data::Dumper 2.121_04
    Filesys::DiskFree NOT INSTALLED
          MIME::Types NOT INSTALLED
            Mail::Cap NOT INSTALLED
         Term::Screen 1.03
      Term::ANSIColor 1.11
       Term::ReadLine Stub
Term::ReadLine::Stub
    ReadLine Features newTTY ornaments tkRunning
                vshnu 1.0211

running on slackware 10.2 kernel 2.6.13

I also made -just in case, this dir in my ~/ coz I saw  some libs can
be in there:
ls ~/lib/perl/Term/
ANSIColor/  ANSIColor.pm  Cap.pm  Complete.pm  ReadLine.pm  Screen.pm
  termcap.pm

any idea why I cannot see vshnu with full colors?

tanks in advance,
Juan

CaFe.pm < http://cafe.pm.org/ >, a Perl Mongers group in Argentina, has
published an interview by Víctor A Rodríguez with Steve Kinzler about
vshnu in their April 2006 bulletin, issue 1.0. It's available online at
< http://cafe.pm.org/boletines/Issue.v1.0.pdf >, with the original English
version at < http://www.cs.indiana.edu/~kinzler/vshnu/perlitas.html >.

An introductory article on using vshnu was published in the
November 2005 issue of Linux Magazine (US version) in Jerry Peek's
Power Tools column, pages 12-17. It's available online now at
<http://www.linux-mag.com/content/view/2332/>.

-sbk

	http://www.cs.indiana.edu/~kinzler/vshnu/
http://www.cs.indiana.edu/~kinzler/vshnu/vshnu-1.0200.tar.gz
vshnu:
# 1.0137 20 Apr 2005 Fix some divide-by-zero errors in empty file sets
# 1.0138 21 Apr 2005 Add $_d and $_dq dotype vars for `file -L` output
# 1.0139 22 Apr 2005 Add &mimetype, $_m and $_mq dotype vars for MIME type
# 1.0140 23 Apr 2005 Change &dotypepath to beep on file not found
# 1.0141 24 Apr 2005 Use V and v options for audio and visual beeps
# 1.0142 27 Apr 2005 Don't show \ as \\ in help keys; Add $typemaptab
# 1.0200 29 Apr 2005 Add mailcap support with Mail::Cap; Add &xsh
vshnucfg:
# 1.0141 20 Apr 2005 Document file variables ($_, $_q, $_r, etc)
# 1.0142 22 Apr 2005 Move 6 cmd to 8; Add 6 cmd for mimetype long listing
# 1.0143 24 Apr 2005 Add V and v options for audio and visual beeps
# 1.0144 26 Apr 2005 Add -safer option to ghostview
# 1.0200 29 Apr 2005 Use &mailcap2typemap for vshnucap and $MAILCAPS, &xsh
If the Mail::Cap, and perhaps MIME::Types, modules are available,
vshnu's supplied configuration will use any mailcap files it finds
(in $MAILCAPS or $HOME/.mailcap, /etc/mailcap, /usr/etc/mailcap and
/usr/local/etc/mailcap) for offered file actions for any file types
it doesn't otherwise cover. Also, it will recognize a vshnu-specific
mailcap file (in $VSHNUCAP or $HOME/.vshnucap or the $default_vshnucap
variable set in the vshnucfg file) for file actions to supersede its
usual configuration. For example, if you prefer xv(1) over display(1)
for viewing image files, you may find adding this line to your vshnucap
file simpler than changing your vshnurc file:
image/*; xv %s; dontneedterminal
-sk

http://www.cs.indiana.edu/~kinzler/vshnu/

What's new since 1.0128?

	 * Improved defaults for pagers
	 * Built-in color df/diskspace listing ("6")
	 * Coloring on alternate long listings
	 * Custom ReadLine completions available
	 * Minor tweaks and bug fixes

See file comments for more details.

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Obconic squama / metathesis subclimax / evertor subsonic.

http://www.cs.indiana.edu/~kinzler/vshnu/

What's new since 1.0124?

vshnu:
# 1.0125   2 Nov 2004 Add $_f and $_fq dotype variables for full pathnames
# 1.0126  27 Nov 2004 Add &filecounts and &filecount
# 1.0127  28 Nov 2004 Color file paths as directories; Add sort bydepth
# 1.0128  31 Jan 2005 Add &expand, &collapse and &expandtoggle aliases

vshnucfg:
# 1.0120   6 Aug 2004 Add Q command for long listing by arbitrary shell cmd
# 1.0121   2 Nov 2004 Add `konqueror` as a browser for tar and zip files
# 1.0122  15 Nov 2004 Add info, list and dump actions for iso files
# 1.0123  19 Nov 2004 Recognize .wmv extension for gmplayer files
# 1.0124  19 Nov 2004 Recognize .st? and .sx? extensions for office files
# 1.0125  23 Nov 2004 Add X cut buffer option to $insertcmd
# 1.0126  26 Nov 2004 Move X cmd to I; Add X command to copy to X cut buffer
# 1.0127  27 Nov 2004 Move Y tree command into dir action menu; Move U to B
# 1.0128  27 Nov 2004 Add Y/U commands to expand/collapse display files
# 1.0129  27 Nov 2004 Add ^Y command for file count reporting
# 1.0130  28 Nov 2004 Add sort by path depth option
# 1.0131  12 Dec 2004 Drop .tsv extension for office files
# 1.0132  31 Jan 2005 Use &expand, &collapse and &expandtoggle aliases

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Hellhound monkeyshine / basin excellence immane / taskwork carburize.

Hi all,

I've just packaged a new version of vshnu available at:

	 http://www.cs.indiana.edu/~kinzler/vshnu/vshnu-1.0124.tar.gz

Here's a summary of what's new since the last release:

# 1.0119  11 Jul 2003   Add df, -V, separate RL hists, /`p, /`d, misc fixes
# 1.0120   4 Dec 2003   Add PGP/GPG actions and LS_COLORS2 support
# 1.0121   3 Jun 2004   Improve default apps; Add ^Z alias, &diskdevs, /`v
# 1.0122   4 Jun 2004   Add `stat` special file action, /A and + commands
# 1.0123   8 Jun 2004   Add &pwd, &diskspace, ^G cmd, .csv and .tsv actions
# 1.0124  29 Jun 2004   Enhance RL M-v for configurable/selectable insertions

Try the new ^G command; try the new + command toggle when you get a
long listing that's truncated on the right; try the new M-v command in
a command line within vshnu (if you have GNU ReadLine) for a choice of
things to insert.

Cheers, 					 Steve

--
from the brain of Steve Kinzler    /o)\    kinzler@...
an organ with a mind of its own    \(o/    www.cs.indiana.edu/~kinzler
Fibrovascular / triggerfish flummery roaster / murid unlovely.

Greetings Vshnu-ers,

Vshnu version 1.0115 is now available

	 http://www.cs.indiana.edu/~kinzler/vshnu/vshnu-1.0115.tar.gz

Upgrade to this version if you've had trouble with vshnu crashing
with Perl 5.8, which handles signals in a new way.  Or if you weren't
getting the hostname in the display.  This version also includes better
integration with Term::ReadLine::Gnu and improved versions reporting
(via vshnu command Ctrl-V).

A new feature is the ability to insert vshnu's current list of chosen
files into a vshnu command line with Meta-V.  This only works if you're
using Term::ReadLine::Gnu.

Regards, 		 Steve Kinzler

--
from the brain of Steve Kinzler    /o)\    kinzler@...
an organ with a mind of its own    \(o/    www.kinzler.com
Steadily aglitter / homer flashgun musicale / hereaway shortsighted.

They're quite rare these days, but vshnu will now work properly on
non-ANSI terminals.

Get Version 1.0106 at
	 http://www.cs.indiana.edu/~kinzler/vshnu/vshnu-1.0106.tar.gz

There isn't really support for non-ANSI color, but you can turn off
color on such a terminal and vshnu will still work okay with just bold
and reverse text.

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Gestate intitule / elaborate primitivism / fusilier woundless.

Sent 30Sep02 from mskowr to kinzler
+---------- Re: [vshnu] no colors ----------
| > http://www.cs.indiana.edu/~kinzler/home/binp/termcolors
| yes it works ok.
| | /usr/local/bin/perl -e 'use Term::ANSIColor; print colored("test\n",
| | "red")'
| yes, the word "test" is in red.

Okay, so far so good ...

| i really want to use vshnu and i guess i'm spolied by color highliting.

vshnu's great with color & I'm sure you can get it to work

| i tried running vshnu with some other terms that and they also don't
| work the way i expected.

Try this now ... within vshnu type ":" to get the "Shell:" prompt, then
type this there:

	 ;print "$ncolors\n"

It should print out a number greater than 1.  If not, your termcap
definition for your terminal isn't claiming color capabilities.
Vshnu believes what your termcap says.

If this is the problem, you may be able to set your terminal type (ie TERM
environment variable) to something like "xterm-16color" or "color_xterm"
or something like that instead of just "xterm" to get it to work --
see your termcap file (usually /etc/termcap or /usr/share/misc/termcap)
for what's available.

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Progeny upwind / demitasse carnivore defile / patentee wattle.

Sent 27Sep02 from mskowr to vshnu
+---------- [vshnu] no colors ----------
| i recently installed vshnu and i can't get any colors.
| my normal xterm displays colors fine -- any suggestions?

Well, first let's test your xterm ...

Download and run this /bin/sh script:

	 http://www.cs.indiana.edu/~kinzler/home/binp/termcolors

Make sure the line that begins with "esc=" has an escape character and
a left square bracket in between the single quotes.  If running this
displays a colorful table, then you've got a terminal with ANSI color
support.

Next, let's test your termcap and perl installation.  Run this command
line, substituting "/usr/local/bin/perl" with the path from the first
line of your installed vshnu script:

/usr/local/bin/perl -e 'use Term::ANSIColor; print colored("test\n", "red")'

It should print the word "test" in red.

Let me know how it goes. 		 -sk

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Marquetry disdain / atheroma muskiness / porter cellarage.

hi

i recently installed vshnu and i can't get any colors.  my normal
xterm displays colors fine -- any suggestions?

thanks.

Minor feature enhancement with this release:

	 ^_ (Control-Underscore) command to list the given (default all)
		 perl variables and their values

This is deep perlishness -- not for the faint of heart.

     http://www.cs.indiana.edu/~kinzler/vshnu/vshnu-1.0103.tar.gz

Comments, improvements welcome.

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Worktable wormseed / sirenian Naomi / homework battleplane.

Vshnu 1.0101 is now available.

	 http://www.cs.indiana.edu/~kinzler/vshnu/
	 http://www.cs.indiana.edu/~kinzler/vshnu/vshnu-1.0101.tar.gz

The most significant enhancement is an interoperation program for the
'bash' command line shell by Marc Schaefer <marc_schaefer@...>.

Note that if you're using the 'tcsh' interoperation setup, you should
review and revise it since it's changed somewhat in how it works.
In particular, you now have to set the VSHNUTMP environment variable
to enable the interoperation, as well as use the new version of the
precmd file.

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Decimate towage / magnification paddy / unfeeling gripsack.

Sent 3Jul01 from karltk to vshnu
+---------- [vshnu] Simple installation problem. ----------
| However, it starts complaining about:
| "Can't find a valid termcap file at /home/karltk/libp/Term/Screen.pm line 230"
| My temporary solution was to fetch
| http://www.tuxedo.org/~esr/terminfo/termtypes.tc.gz
| and install it as ~/.termcap.

Thanks for pointing this out.  I've added the following to vshnu's
installation instructions, "Prerequisites" section:

     Term::Screen uses Term::Cap, so you'll need a termcap file containing
     your terminals' capabilities definitions.  Most systems already
     have one, but if yours doesn't, a very complete termcap file is
     available at <http://www.tuxedo.org/~esr/terminfo/termtypes.tc.gz>.
     A much briefer one containing only some common terminals is
     at <http://www.cs.indiana.edu/~kinzler/home.html#etc/termcap>.
     The termcap file may be installed as $TERMCAP, $HOME/.termcap,
     /etc/termcap or /usr/share/misc/termcap.

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Bechamel tipstock / translative lowborn reeding / sawbuck ropedancer.

Hi people.


I downloaded vshnu-1.0010 just a few minutes ago but it seems to be a bit
uncooperative.

I hardlinked libperl/Term/{Screen,ANSIColor} to
~/libp/Term/{Screen,ANSIColor}.pm, and this stopped the vshnu script from
complaining about missing Screen and ANSIColor

However, it starts complaining about:
"Can't find a valid termcap file at /home/karltk/libp/Term/Screen.pm line
230"

An strace tells me it's looking for /etc/termcap. Termcap seems to be
superceded by terminfo in most distros.

My temporary solution was to fetch
http://www.tuxedo.org/~esr/terminfo/termtypes.tc.gz
and install it as ~/.termcap.

It would probably be a smart move to go for terminfo for newer releases.


Regards,
Karl T

Prompted by Georges' query last week about function key support in vshnu,
I investigated further and found it was quite worthwhile to support it
more officially.

Hence, vshnu 1.0010 has improved function key support and default
definitions for INSERT, DELETE, HOME, END, PAGEUP, PAGEDOWN and the 4
arrow keys.  F1 through F12 are left for personalized use.

     http://www.cs.indiana.edu/hyplan/kinzler/vshnu/vshnu-1.0010.tar.gz

	 del     slide the bag backward on the screen
	 end     shift the file display left one column
	 home    cd to the user's home directory
	 ins     slide the bag forward on the screen
	 kd      slide the bag down on the screen
	 kl      slide the bag left on the screen
	 kr      slide the bag right on the screen
	 ku      slide the bag up on the screen
	 pgdn    slide the point down one file
	 pgup    slide the point up one file

Enjoy, 						 Steve

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Krishnaism overdose / preoccupy gallonage / opportunity.

Sent 23Jun01 from gc to kinzler
+---------- vshnu ----------
| I installed vshnu some weeks ago, and now I use it more than my file
| manager or any term. I think it doesn't have the success it deserves
| (and it made me begin to learn perl).

Hi Georges.  Thanks, that's all great to hear!

| I have personalized it but I would like to go a little further and make
| use of PgUp, PgDn, and the arrow keys to navigate when in main mode.
| Having seen that I could use \040 and \177 for space and delete, I tried
| \121 (PgDn) but it doesn't work (is \121 PgDn or Q ? Q doesn't work too).

Yes, \121 is "Q".  What a special function key like PgDn sends can vary
from system to system, I believe.  Mine actually sends 4 characters
( <Ctrl-[> [ 6 ~ ) when you hit PgDn (this is probably pretty standard
for PC-type keyboards with xterm).

| Is there some way to do that ?

Actually, there is something you can try and if it works, you can define
and use the function keys very easily.  If it doesn't then it'll take
lots more trickery.  Because I didn't expect it to work for everyone
everywhere and since I prefer to avoid using them myself, I didn't define
or use any function keys in vshnu's distributed code.

But, of course, you can always do so in your own personalizations.

The screen module is really where function keys should be recognized.
Term::Screen, the basic one vshnu uses, does have some limited support
for function keys, so you can use it if it works for you.

Here's how to test -- just add this to your .vshnurc:

	 $keymap_{"pgup"} = 'msg "Hey, you hit Page Up!"';

reload, and hit PgUp in vshnu main mode.

See the end of the Term/Screen.pm file for the other function key names.

| You must be a very busy man, so excuse me for bothering.
| Thank you (at least for that fantastic little program).

No problem, and you're welcome :-)

And if you come up with any useful personalizations or a good set of
definitions for the function keys, send them along or share them with
the mailing list.

Cheers, 					 Steve

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Hardiness deerfly / nougat ordinance noontime / springer unsafety.

Hi all,

Vshnu 1.0009 is a minor functional enhancement release:

1.0009  15 Jun 2001   Added loading of .vshnu* files via typemap
1.0008  06 Jun 2001   Added `rpm -Fhv` freshen option for rpm files
1.0007  29 May 2001   Recognize .\d\w exts as man pages; "go perl:" support
1.0006  27 Apr 2001   Improved Slashdot interface in vshnurc
1.0005  26 Jan 2001   Use most specific LS_COLORS match and "--color=yes"
1.0004  25 Jan 2001   Added ReadLine package to ^V command output
1.0003  13 Dec 2000   Version format x.y.z -> x.0y0z; s/.pm// in libperl
1.0002  05 Dec 2000   Added 'sleep 1' to backgrounded commands; *bz2 support
1.0001  15 Nov 2000   Color text pager defaults to `less -r` if PAGER=less
1.0000  07 Nov 2000   Initial public release

Available at

	 http://www.cs.indiana.edu/hyplan/kinzler/vshnu/vshnu-1.0009.tar.gz

Cheers, 					 Steve

--
from the brain of Steve Kinzler    /o)\    steve@...
an organ with a mind of its own    \(o/    www.kinzler.com
Snuggery diphyodont / toxic bother gynandrous / heroism unguard.

Hello, all.  Vshnu 1.0005 is now available.

	 http://www.cs.indiana.edu/hyplan/kinzler/vshnu/
	 http://www.cs.indiana.edu/hyplan/kinzler/vshnu/vshnu-1.0005.tar.gz

This contains only minor, optional tweaks and fixes on the last announced
vshnu (1.0.1).  Details follow:

vshnu:
# 1.0003  13 Dec 2000 Version format x.y.z -> x.0y0z
# 1.0005  26 Jan 2001 Use most specific LS_COLORS match

vshnucfg:
# 1.0002  05 Dec 2000 Added 'sleep 1' to /D command; *bz2 support
# 1.0003  13 Dec 2000 Version format x.y.z -> x.0y0z
# 1.0004  25 Jan 2001 Added ReadLine package to ^V command output

vshnurc:
# 1.0002  04 Dec 2000 Added 'sleep 1' to /Z command
# 1.0003  13 Dec 2000 Version format x.y.z -> x.0y0z
# 1.0004  25 Jan 2001 Added ReadLine package to ^V command output
# 1.0005  26 Jan 2001 Appended "=yes" to "--color"s

--
from the brain of Steve Kinzler    /o)\    kinzler@...
an organ with a mind of its own    \(o/    www.cs.indiana.edu/~kinzler
Eductor drysalter / gilbert furfuran install / inanity bombard.

It should be noted that one of the prerequisites for vshnu,
Term::Screen, does not install Screen.pm in
/perl/lib/directory/Term/Screen.pm
but instead installs it in
/perl/lib/directory/Screen.pm.

This results in an error when one runs a make for vshnu. Screen.pm
must be manually copied into

/perl/lib/directory/Term.

Not strictly a vshnu note, but someone ought to be made aware of it.

Jonathan Cohen

Sent 29Nov00 from jkohen to kinzler
+---------- Vshnu and Termcap ----------
| I was going to give your program a try, but it choked because my system
| doesn't have a termcap file. Sure I can generate one from the terminfo
| sources, but why going back to an obsolescent thing? Is there an easy
| way to convert VSHNU to using Curses instead? I could help doing so if
| you think it won't be a pain in the ass :)

Hi, Javier.  Yes, vshnu uses Term::Screen which uses the termcap model.
One reason I choose that is because it requires just a single portable
Perl module file and I wanted to keep vshnu trivial to install on any
Unix.  I knew it wouldn't port to non-Unices, but figured all Unices
could handle termcap, so I'm really curious about what type of system
you have where this is a concern?

I wonder if Curses won't lead to bigger installation/portability concerns,
though?  Maybe the best solution is to enhance Term::Screen to work with
terminfo, too ...

If you want to work on adding Curses support to vshnu, it shouldn't
be hard -- vshnu's screen handling is very basic.  I'd hope to see
it implemented as an optional alternative to Term::Screen, ie no new
required modules to run vshnu, etc.

Anyone got a better solution?

Steve

--
from the brain of Steve Kinzler    /o)\    kinzler@...
an organ with a mind of its own    \(o/    www.cs.indiana.edu/~kinzler
Scriptwriter auric / laryngitis botheration / winner sermonize.

Hi, all.  I've made a small upgrade to the vshnucfg.pl file so it should
work better when your $PAGER is set to "less".  In particular, the color
text pager $cfg::pagerr will now default to "less -r", so you don't have
to specifically reconfigure that to view the online help, etc.

	 www.cs.indiana.edu/~kinzler/vshnu/vshnu-1.0.1.tar.gz

--
from the brain of Steve Kinzler    /o)\    kinzler@...
an organ with a mind of its own    \(o/    www.cs.indiana.edu/~kinzler
Topaz celloidin / leasehold percept steadily / dirtiness sonar.

Sent 15Nov00 to kinzler
+---------- Re: vshnu is nice ----------
| How does one copy files? Move files? Is there a wildcard expansion for
| the list of selected files? (if there isn't, 'mv ~/foo' doesn't work in
| chooser mode, as it expands to ( 'mv ~/foo bar1 bar2 bar3 ...' ), instead.

I still use cp(1) and mv(1) commands.  They're short and flexible enough
for me to still want to use directly.  But vshnu can facilitate their use.

If I want to run `mv bar1 bar2 bar3 ~/foo`,

I may choose bar* with 	 /.^bar<Return>
(note that you enter a regular
  expression here ala sed/vi/perl,
  not a shell pattern) [handy mnemonic
  here for "choose by regexp" =
  slashdot, a favorite website :-]

then do the mv command with  ;mv<Return>~/foo<Return>
(the chosen files are inserted
  into the command between the two
  segments, the latter of which may
  often be empty)

Alternately, you could also choose ~/foo lastly and then just type
";mv<Return><Return>" in choose mode.  To review your full current choose
list you can type <Ctrl-C> (again to get back).

Cheers, 					 Steve

--
from the brain of Steve Kinzler    /o)\    kinzler@...
an organ with a mind of its own    \(o/    www.cs.indiana.edu/~kinzler
Bibliography / imagination Orpington / heavyhearted maya.

Sent 14Nov00 from tingley to vshnu
+---------- [vshnu] less -R ----------
| Congratulations Mr. Kinzler, this is pretty cool.

Thanks, glad you like it.

| A minor issue -- the vshnurc.pl is currently using 'less -R' as a default
| for raw input:
|
|     $cfg::pagerr = 'less -R';    # raw pager for colored text
|
| On the incarnation of less that I have available (340), '-r' is for raw
| input, and -R makes vshnu die.  I don't know how many different less
| semantics are floating around.

I think the semantics are consistent -- I'm just using a newer version
of less (358) and have no trouble with -R.  'less -r' should work fine
for you, instead, though.  -R is just a little smarter when viewing
lines of text that wraparound.

Cheers, 					 Steve

--
from the brain of Steve Kinzler    /o)\    kinzler@...
an organ with a mind of its own    \(o/    www.cs.indiana.edu/~kinzler
Umlaut colchicum / causeway lira sardius / gatefold vocalism.

> the directory display?  There are options to hide ./.. and "backup files",
> but no general way to hide all files starting with '.'.  I'm sure I'll be
> able to find something if I dig around in the config files long enough.

| a       don't list dot files

*sigh* never mind :)

ct

Congratulations Mr. Kinzler, this is pretty cool.

A minor issue -- the vshnurc.pl is currently using 'less -R' as a default
for raw input:

     $cfg::pagerr = 'less -R';    # raw pager for colored text

On the incarnation of less that I have available (340), '-r' is for raw
input, and -R makes vshnu die.  I don't know how many different less
semantics are floating around.

Also, is there an easy way to toggle the listing of "invisible" files in
the directory display?  There are options to hide ./.. and "backup files",
but no general way to hide all files starting with '.'.  I'm sure I'll be
able to find something if I dig around in the config files long enough.

ct

It's a beautiful day in this neighborhood,
A beautiful day for a neighbor.
Would you be mine?
Could you be mine?