LispWorks IDE - automatically open files

Hello!

Everytime I start my LispWorks environment I have to open some files so that they are open in the editor. But it is uncomfortable for me to open every file individually via File -> Open -> Navigate to it -> Open.

Does anyone have a hint how to improve this?

And is there an easier way to jump between the open files instead of clicking to Buffers or via History -> Items?

best regards,

Phil

Re: LispWorks IDE - automatically open files

Am 29.09.13 14:04, schrieb Philipp Bach:
> Hello!
>
> Everytime I start my LispWorks environment I have to open some files so
> that they are open in the editor. But it is uncomfortable for me to open
> every file individually via File -> Open -> Navigate to it -> Open.
>
> Does anyone have a hint how to improve this?
>
> And is there an easier way to jump between the open files instead of
> clicking to Buffers or via History -> Items?
>
> best regards,
> Phil

Use Emacs keys

C-x C-f

C-x C-b

~jens

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: LispWorks IDE - automatically open files

Something no-one has quite said is that one trick for doing this is to define a system with the files you are interested in – assuming they are all related they probably belong in a system anyway – and then load the system definition.  Then you can easily edit the source of any of the files via the system browser.

--tim

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: LispWorks IDE - automatically open files

Thank you all for your advice. The (ed "Path/To/File") was exactly what I was looking for!

best regards,

Phil

On Sun, Sep 29, 2013 at 3:22 PM, Tim Bradshaw <tfb@cley.com> wrote:

Something no-one has quite said is that one trick for doing this is to define a system with the files you are interested in – assuming they are all related they probably belong in a system anyway – and then load the system definition. Then you can easily edit the source of any of the files via the system browser.

--tim