| Re: question about paths/workspace [message #57253 is a reply to message #57248] |
Wed, 05 December 2007 15:19   |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Dec 5, 5:15 pm, Vince Hradil <hrad...@yahoo.com> wrote:
> On Dec 5, 5:07 pm, Vince Hradil <hrad...@yahoo.com> wrote:
>
>
>
>> On Dec 5, 4:41 pm, "R.G. Stockwell" <noem...@please.com> wrote:
>
>>> "Vince Hradil" <hrad...@yahoo.com> wrote in message
>
>>> news:ad45793c-59f1-4ce3-af1b-1562b8811b23@v4g2000hsf.googleg roups.com...
>
>>>> On Dec 5, 2:02 pm, "R.G. Stockwell" <noem...@please.com> wrote:
>>>> > "Vince Hradil" <hrad...@yahoo.com> wrote in message
>
>>>> > news:5896e153-b4ef-4f90-882f-6848389bf05a@r60g2000hsc.google groups.com...
>
>>>> > > On Dec 5, 12:16 pm, "R.G. Stockwell" <noem...@please.com> wrote:
>>>> > >> I have my idl code on a networked raided backedup drive,
>>>> > >> but often take my laptop away from that network.
>
>>>> > >> So I have my path setup to look for the network first (drive H say)
>>>> > >> then look on the laptop (drive C). It works pretty well.
>
>>>> > >> If I put my 'workspace' on H, and am off the network,
>>>> > >> I get 'workspace cannot be found' errors and it forces
>>>> > >> me to create a new one.
>
>>>> > >> Anyone have a good solution to using travelling workspaces?
>>>> > >> I haven't really looked into the problem much yet, maybe it's
>>>> > >> a stupid question with an obvious answer.
>
>>>> > >> Cheers,
>>>> > >> bob
>
>>>> > > Can you just create your workspace on the C-drive, but create projects
>>>> > > from your remote (H) drive. The workspace won't copy the files from
>>>> > > the H-drive, but just keep a reference to them.
>
>>>> > Short answer, no. Not if I want to access my workspace
>>>> > from somewhere other than my laptop (which I often do).
>>>> > The C drive is only accessible from the laptop.
>
>>>> > Cheers,
>>>> > bob
>
>>>> How about just making workspaces everywhere that point to the same
>>>> projects? Isn't a workspace just a group of projects?
>
>>> We'll see how it goes. I am worried about pointing to a project that
>>> "isn't there", but I have not done that yet.
>
>>> Cheers,
>>> bob
>
>> Well, I tried it. If the project "isn't there" I get an error that
>> the workspace is in use - pick another one. Oh, well that won't work
>> do all!
>
> Wait a minute... It seem that the IDLDE process just didn't stop. I'm
> trying again. I'll let you know what happens.
>
> It seems that the background process of "Analyzing code..." continues
> after I quit the IDLDE - I have a fairly large path, and it takes
> several minutes to "analyze", so during this testing I quit IDL before
> the background process was finished - That locks the IDLDE workspace.
> This is not acceptable. I think that 7.0.1 needs to have a "Analyzing
> code..." work-around. Oh for my command line and emacs...
The process is still there, with about 1/2 Mb virtual memory used,
even though it seems the Analyzing code is done. I'm going to kill it
and disconnect the remote drive. And test the workspace again.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
