[Xastir-dev] Why change working directory?

Jack Twilley jmt at twilley.org
Fri Dec 5 00:50:33 EST 2003


WARNING: Unsanitized content follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Curt" == Curt Mills <Curt> writes:

Jack> I had a surprise recently trying to import a log file.  I
Jack> assumed that since I had started xastir while in my home
Jack> directory that I could import a file from my home directory
Jack> without specifying the full path.  It turns out that entering
Jack> "log.txt" causes xastir to look in "~/.xastir/log.txt".  Also,
Jack> core files generated by xastir end up in ~/.xastir/ on my
Jack> system.  This strongly implies that we change the working
Jack> directory in the system.  Any particular reason?

Curt> Yea.  Because when you want to open up a log file, you'd better
Curt> be where the log files are.  Saves a bit of work for the user.

Unless, of course, the user knows where their log files are, and tries
to get there.  Bah. :-)

Jack> Oh, and on a side note -- lots of changes were discussed to
Jack> permit using user-specific maps directories in addition to
Jack> system map directories.  Was this ever fully implemented?

Curt> Nope.

Darn.

Curt> One can add a symlink to their home directory from the system
Curt> maps directory, then make the directories that it points to only
Curt> readable by the user.  Similar effect, but less to change in the
Curt> software.

Not the same effect at all, actually.

Jack.
- -- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/0ByuGPFSfAB/ezgRAmKWAJ9Cb/iR3RPso5L8S35PV144TiR4nACfdQJb
IUu42RyR7bWD9Y6gIRqvp8o=
=K3o4
-----END PGP SIGNATURE-----



More information about the Xastir-dev mailing list