Pathname bug in Edit 3.0

Thread View: comp.sys.next.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Alexander Lehmann Mon, 12 Oct 1992 14:52

#1430

Author: Alexander Lehmann
Date: Mon, 12 Oct 1992 14:52

31 lines
1383 bytes

I ran accross a bug in NS3.0's Edit.

When one tries to open a file that is contained in a directory that is linked
somehow that path gets messed up.

For Example:

% cd /usr/adm
% open daily

leads to an error requester "Can't open file /adm/daily"

however:

% open /usr/adm/daily

works, but the title bar display the name as "/adm/daily".

This seems to be due to the new scheme of displaying names with ~.

Since this is done by other applications as well, maybe this could be a routine
in the shared libraries which could maybe be fixed in the library, but if this
is code that is compiled into the different applications, this is probably to
complicated.

If anyone can point out the location (or name) of this function, I'll try to fix
it.

-- 
Alexander Lehmann                      | "Wopp"
alexlehm@iti.informatik.th-darmstadt.de|         -  ( THHGTTG Pt.3 )

Re: Pathname bug in Edit 3.0

#1451

Author: Moises Oliveira
Date: Tue, 13 Oct 1992 01:31

42 lines
2126 bytes

In article <1992Oct12.145220.35716@news.th-darmstadt.de> alexlehm@iti.informatik.th-darmstadt.de (Alexander Lehmann) writes:

> I ran accross a bug in NS3.0's Edit.

Actually this bug has nothing to do with Edit.

There is a set of three known bugs involving

/usr/bin/open
/usr/bin/openfile
and /NextDeveloper/Apps/ProjectBuilder.app

The bug is basically this: Someone decided that the /private
directory is something you shouldn't have to ever see.  If you try
to open a file under /private, the /private is stripped from the
name of the file you are opening.  Thus if you try to open a file
named /private/tmp/foo, it will munge the name to /tmp/foo.  Which
will work for things like /tmp, but not for other directories.

>For Example:
>% cd /usr/adm
>% open daily

/usr/adm is really /private/adm.  Thus it strips it down to
/adm/daily, which doesn't exist.  You also can't open stuff in
/usr/spool, /usr/preserve, /private/tftpboot, or /private/vm.

>Since this is done by other applications as well, maybe this could be a routine
>in the shared libraries which could maybe be fixed in the library, but if this
>is code that is compiled into the different applications, this is probably to
>complicated.

Again, Edit is not the problem, nor are the shared libraries.

>If anyone can point out the location (or name) of this function, I'll try to fix
>it.

As far as /usr/bin/open and /usr/bin/openfile go, the easiest task
is to probably replace them with the 2.0 versions.  The 3.0 versions
have no new features, just new bugs. If you don't have 2.0 versions,
you can use a sector editor to patch out the /private string.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads