Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.acorn.programmer > #5847 > unrolled thread
| Started by | Richard Ashbery <basura@invalid.addr.uk> |
|---|---|
| First post | 2019-10-20 13:44 +0100 |
| Last post | 2019-10-20 15:36 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to comp.sys.acorn.programmer
Set working directory Richard Ashbery <basura@invalid.addr.uk> - 2019-10-20 13:44 +0100
Re: Set working directory Steve Fryatt <news@stevefryatt.org.uk> - 2019-10-20 14:54 +0100
Re: Set working directory Richard Ashbery <basura@invalid.addr.uk> - 2019-10-20 15:36 +0100
| From | Richard Ashbery <basura@invalid.addr.uk> |
|---|---|
| Date | 2019-10-20 13:44 +0100 |
| Subject | Set working directory |
| Message-ID | <5805eb497bbasura@invalid.addr.uk> |
I can set the current working directory by clicking into the directory where my BASIC files are held and use 'Set directory' from the 'Filer' window. I often forget so when I run the first program containing a CHAIN keyword it fails (can't find next program). It would be easier to double-click an obeyfile (perhaps called !RUN_FIRST) to do this but the one tried below doesn't work. Pseudo application directory with !Boot and !Run obeyfiles containing... Set Graphics_sequence$Dir <Obey$Dir>.^ (!Boot) /<Obey$Dir>.!Boot (!Run) Any solution please?
[toc] | [next] | [standalone]
| From | Steve Fryatt <news@stevefryatt.org.uk> |
|---|---|
| Date | 2019-10-20 14:54 +0100 |
| Message-ID | <mpro.pzoelw02gb5vo01xa.news@stevefryatt.org.uk> |
| In reply to | #5847 |
On 20 Oct, Richard Ashbery wrote in message
<5805eb497bbasura@invalid.addr.uk>:
> I can set the current working directory by clicking into the directory
> where my BASIC files are held and use 'Set directory' from the 'Filer'
> window. I often forget so when I run the first program containing a CHAIN
> keyword it fails (can't find next program). It would be easier to
> double-click an obeyfile (perhaps called !RUN_FIRST) to do this but the
> one tried below doesn't work.
If all you're trying to do is set the current working directory, then surely
an obey file containing simply
Dir <Obey$Dir>
would do it?
If you add back in the complexity of the application folder, then
Dir <Obey$Dir>.^
would set the directory to that within which the application lives. I'm not
sure why you need that, though.
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
[toc] | [prev] | [next] | [standalone]
| From | Richard Ashbery <basura@invalid.addr.uk> |
|---|---|
| Date | 2019-10-20 15:36 +0100 |
| Message-ID | <5805f586d6basura@invalid.addr.uk> |
| In reply to | #5848 |
In article <mpro.pzoelw02gb5vo01xa.news@stevefryatt.org.uk>, Steve Fryatt <news@stevefryatt.org.uk> wrote: > On 20 Oct, Richard Ashbery wrote in message > <5805eb497bbasura@invalid.addr.uk>: > > I can set the current working directory by clicking into the > > directory where my BASIC files are held and use 'Set directory' > > from the 'Filer' window. I often forget so when I run the first > > program containing a CHAIN keyword it fails (can't find next > > program). It would be easier to double-click an obeyfile (perhaps > > called !RUN_FIRST) to do this but the one tried below doesn't > > work. > If all you're trying to do is set the current working directory, > then surely an obey file containing simply > Dir <Obey$Dir> > would do it? > If you add back in the complexity of the application folder, then > Dir <Obey$Dir>.^ > would set the directory to that within which the application lives. > I'm not sure why you need that, though. I vaguely remember I had a method that did this and the one I dug up was the one above (I believe from Martin Bazley). Method seemed hugely over complicated and doesn't work anyway. Yes of course you are right Dir <Obey$Dir> is all that's needed. I've done this before but forgotten how - very annoying I should forget a simple thing like that. Many thanks Steve Richard
[toc] | [prev] | [standalone]
Back to top | Article view | comp.sys.acorn.programmer
csiph-web