TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: All
from: Bob van der Poel 76510,2203
date: 1993-03-06 17:23:39
subject: #CHD problems

#: 17633 S12/OS9/68000 (OSK)
    06-Mar-93  17:23:39
Sb: #CHD problems
Fm: Bob van der Poel 76510,2203
To: All

I've had more than one person make a request for a change in the way VED
handles reading and switching directories. Currently, when its file selector is
feed a directory name it just calls the C chd() function. This makes stepping
though directories pretty simple. However, it has a problem:

The application has no idea what the original directory was. This means that if
someone is in the directory a/b/c/d when the program starts, loads a file
'foo', makes some changes, then reads in another file using the file selector
and changes directories... when 'foo' is saved it will be in the new, not
original, directory.

This gets to be a bother when multiple buffers are being used. One buffer might
be editing 'foo' from the directory VED was in when started; a 2nd buffer might
be editing 'woof' from '....../a/b'. Just saving the files will put them both
in '....../a/b'. Probably not what the doctor ordered.

I guess that what I need is a pushdir() function. Then the file selector could
do all the chd()s it wants. When a file is selected, the pushdir() information
could be saved with the filename. Then, when a save it done it could restore
the file to the correct directory.

The only other method I see is to manually keep track of the path
names--appending directory names to a pathlist as the directoy is stepped
though. But that becomes real complicated real fast...after all, isn't that why
we have an OS?

Any ideas, suggestions, comments, etc. will be appreciated.

There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.