[prev in list] [next in list] [prev in thread] [next in thread] 

List:       unison-users
Subject:    [unison-users] text interface improvements?
From:       Martin =?iso-8859-1?Q?B=E4hr?= <mbaehr () email ! archlab ! tuwien ! ac ! at>
Date:       2004-05-28 1:29:05
Message-ID: 20040528012905.GG29872 () email ! archlab ! tuwien ! ac ! at
[Download RAW message or body]

hi,

i have a few questions/suggestions regarding the command-line interface:


when going through the files you use a lot of commands that produce text
output (such as d, x, l ...) at the end it is hard to have an overview
of all the changes that will happen,

so when unison asks:
Proceed with propagating updates? [] ?

it would be nice to get a repeated list summarizing what files
will be synchronized in which direction.

  s               show a summary of all updates


with the option -auto it would be convenient if selecting "n" on the
proceed question would then go back into normal mode going through all
selections (turning -auto off)

this would allow to correct wrong decisions unison makes while being
able to rely on them being right most of the time. the current
workaround is to quit, remove ­auto from the commandline and run again.

alternatively another command could be added for this.


when the two roots have long names (which usually seems to happen when
both are local) they are currently abbreviated. this is not very
helpfull if they are similar. it would be preferable to always show them
in the full length even if multiple lines are needed.


the error
  $ unison . Mail /media/vg40/lvol1/backup/tomoyo/Mail
  Uncaught exception Sys_error("Is a directory")
is not very helpful.
better would be: "." is not a profile
or something along those lines.


could additional arguments be interpreted as path, to allow examples like:
  unison . -path travel -path src -path Mail ssh://destination/
be shortened to:
  unison . travel src Mail ssh://destination/
possibly even making the first root implicit?
(last argument is the second root, and if there is more than two
arguments they are all paths with the first root being the current
directory)


POSIX spec has this feature where appending / to a path means that if
path is a link, then follow that link:
lrwxrwxrwx    1 mbaehr   mbaehr          3 May 28 03:23 bar -> foo

cp bar baz (copy the link "bar")
cp bar/ baz (copy the directory "foo")

if unison would support that, it would reduce the need to use -follow in
cases like this one (which i am actually using now):
  unison . -path travel -path Mail -follow "Name Mail" /destination
(btw, it took me a while to figure out that i needed to quote the
argument to -follow)


apart from that sofar unison is an excellent tool.
it is amazing how i could have missed it for such a long time.

greetings, martin.
-- 
looking for a job doing pike programming, sTeam/caudium/pike/roxen training,
sTeam/caudium/roxen and/or unix system administration anywhere in the world.
--
pike programmer   travelling and working in europe            open-steam.org
unix system-      bahai.or.at                       iaeste.(tuwien.ac|or).at
administrator     (stuts|black.linux-m68k).org                  is.schon.org
Martin Bähr       http://www.iaeste.or.at/~mbaehr/


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/26EolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/unison-users/

<*> To unsubscribe from this group, send an email to:
     unison-users-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
 

[prev in list] [next in list] [prev in thread] [next in thread]