The ability for workgroups2 to save programming language interpeters about workgroups2

[pashinin]

Thanks for the report. I'll look carefully at it later.
For now - I've writen an article for you (and maybe others) - https://github.com/pashinin/workgroups2/wiki/How-to-restore-a-specific-type-of-buffer
It may help to implement this support faster.

[pashinin]

I was able to restore these shells (with last commit): R, Prolog, Python. With basic support they are just started with current directory they had.

[pashinin]

Have you tried an updated version?

[codekingplusplus]

I will either this weekend or next weekend. Unfortunately, (well I guess fortunately too) I have a decent amount of responsibilities or else I might seriously play with emacs all day. It is so much fun but can be very distracting. I am also new to emacs in the sense that I cannot allocate 10 minutes here and say I'll get it done then. It would take me some googling and such.

[pashinin]

No problems! Take your time

[codekingplusplus]

I updated my emacs packages a little later than expected, but it works very well! Thank you very much. One of these days I may get around to modifying a few pieces of the package myself.

For example, it would be nice to keep a list where we could add which interpreters/programs to keep in buffers besides the few I mentioned.

The only thing that seems odd to me is the following which is best explained by example:

I have two workgroups, wg1 and wg2. I load the default workgroup (wg1) on starting emacs (which is a config file named emacs_def.wg), wg2 is also maintained in the active workgroups list when loading emacs_def.wg. So after loading, I switch to wg2 and then open the scratch buffer which is in Fundamental mode. I want the scratch buffer to be in lisp-interaction-mode so I do that. Then I save with C-c w C-s and emacs says: 'Saved emacs_def'. I proceed to close and reopen emacs, switch to wg2 and see that the scratch buffer is still in fundamental mode; even after I saved. -- What went wrong here?

[pashinin]

Nice question but nothing is wrong here.
If a buffer exists - WG just opens it.
I don't know why your *scratch* buffer is Fundamental, mine is lisp (even for emacs -Q)

WG doesn't save modes. Instead it relies on your settings.
So WG opens a file - Emacs chooses a mode for it.

Modes are just hints to use a correct way to save/restore a buffer.

[codekingplusplus]

Can we add support for more interpreters/programs? For example mathematical softare such as SAGE: http://en.wikipedia.org/wiki/Sage_%28mathematics_software%29 and other programming languages such as scheme and common-lisp?

Perhaps we can make this more general. I think you need an ID and a PATH? for each program. Let me know what you need and then we can get started.

[codekingplusplus]

Here is an implementation detail I think would be useful:

How about we provide something along the lines of a configuration file? I'm not too experienced with emacs but I remember when I was debugging something through the help pages I was interlinked to something like a config file for the package I was debugging. Perhaps this was called custom-set-variables?

A good reason for this is customization and flexibility, e.g. I just switched to the IPython interpreter so now I have to get that opening when emacs loads.

[pashinin]

Do you want to make support of new additional buffers == part of WG configuration?
If so - it's a great idea! And maybe... some day...
Also note - it's better to open a new issue for each problem and request (even small).

[codekingplusplus]

Yes, if you mean users can set these special buffers as part of a
configuration then yes. If that is too big of an undertaking, perhaps we
can just work on adding support to a few more programs/interpreters.

For example, I think a quick fix for me would be changing the python
interpreter to IPython. I am currently looking in:
workgroups-specialbufs.el
at functions
wg-serialize-python-shell-buffer and
wg-deserialize-python-shell-buffer

What is the quick fix to change this to the IPython interpreter instead of
the default one?
**

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 3:45 PM, Sergey Pashinin
[email protected]:

Do you want to make support of new additional buffers == part of WG
configuration?
If so - it's a great idea! And maybe... some day...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-26680843
.

[codekingplusplus]

Wait, nvm I was not thinking and the IPython thing works!

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 4:13 PM, Steve Styer [email protected] wrote:

Yes, if you mean users can set these special buffers as part of a
configuration then yes. If that is too big of an undertaking, perhaps we
can just work on adding support to a few more programs/interpreters.

For example, I think a quick fix for me would be changing the python
interpreter to IPython. I am currently looking in:
workgroups-specialbufs.el
at functions
wg-serialize-python-shell-buffer and
wg-deserialize-python-shell-buffer

What is the quick fix to change this to the IPython interpreter instead of
the default one?
**

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 3:45 PM, Sergey Pashinin <[email protected]

wrote:

Do you want to make support of new additional buffers == part of WG
configuration?
If so - it's a great idea! And maybe... some day...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-26680843
.

[codekingplusplus]

But the other most helpful interpreter would be common-lisp which I run by
using SLIME mode (M-x slime)

Sorry for exploding your inbox!

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 4:19 PM, Steve Styer [email protected] wrote:

Wait, nvm I was not thinking and the IPython thing works!

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 4:13 PM, Steve Styer [email protected] wrote:

Yes, if you mean users can set these special buffers as part of a
configuration then yes. If that is too big of an undertaking, perhaps we
can just work on adding support to a few more programs/interpreters.

For example, I think a quick fix for me would be changing the python
interpreter to IPython. I am currently looking in:
workgroups-specialbufs.el
at functions
wg-serialize-python-shell-buffer and
wg-deserialize-python-shell-buffer

What is the quick fix to change this to the IPython interpreter instead
of the default one?
**

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 3:45 PM, Sergey Pashinin <
[email protected]> wrote:

Do you want to make support of new additional buffers == part of WG
configuration?
If so - it's a great idea! And maybe... some day...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-26680843
.

[codekingplusplus]

Also, how did you learn so much about emacs systems programming? I would
like to take the time and become more proficient (just the little things I
do know and the enjoyment of the environment makes my programming and life
easier/happier/efficient). with emacs; however this probably wouldn't
happen till a holiday or my summer vacation.

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 4:22 PM, Steve Styer [email protected] wrote:

But the other most helpful interpreter would be common-lisp which I run by
using SLIME mode (M-x slime)

Sorry for exploding your inbox!

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 4:19 PM, Steve Styer [email protected] wrote:

Wait, nvm I was not thinking and the IPython thing works!

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 4:13 PM, Steve Styer [email protected] wrote:

Yes, if you mean users can set these special buffers as part of a
configuration then yes. If that is too big of an undertaking, perhaps we
can just work on adding support to a few more programs/interpreters.

For example, I think a quick fix for me would be changing the python
interpreter to IPython. I am currently looking in:
workgroups-specialbufs.el
at functions
wg-serialize-python-shell-buffer and
wg-deserialize-python-shell-buffer

What is the quick fix to change this to the IPython interpreter instead
of the default one?
**

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Sun, Oct 20, 2013 at 3:45 PM, Sergey Pashinin <
[email protected]> wrote:

Do you want to make support of new additional buffers == part of WG
configuration?
If so - it's a great idea! And maybe... some day...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-26680843
.

[pashinin]

That's the question now:
http://stackoverflow.com/questions/19561073/how-to-detect-what-shell-is-running-in-emacs-comint-mode

Also, how did you learn so much about emacs systems programming?

I've used Emacs each day for about an year now.

[pashinin]

Check it when Melpa updates. slime was started for me.
About restoring any shells... each shell can execute the code specific to it (like hooks or other code) and (I think) we can't automatically determine it.
So for now I will just add support for each mode you ask. Please open a new issue each time.

[codekingplusplus]

Thanks! All I need for now is:

SAGE
slime (common-lisp)

or did you already do this?

[pashinin]

Only slime

[pashinin]

Although I had some errors starting sage-mode - https://bitbucket.org/gvol/sage-mode/issue/29/symbols-value-as-variable-is-void-comint - I hope restoring it's buffer will work now

[codekingplusplus]

Sergey,

I can see that Sage would like to work, but I am having problems with it
too. It hangs on "Sent python-eldoc-setup-code" When it freezes there it
stops emacs from loading anything else. I guess there is nothing we can do
about that...

Other than that it seems to work good, my only issue is that the CL-REPL
chooses a random window to open in each time (this does not happen with the
python interpreter -- as the python interpreter always opens in the same
window in which I save my session). Recall that I split my emacs screen
into 4 windows.

One request: Is it possible to specify via command line which workgroup I
want to open? Right now I have two workgroups. I use one for work related
tasks, and the other for math.

WG1:

Thanks for all the good work :)

On Fri, Oct 25, 2013 at 6:21 PM, Sergey Pashinin
[email protected]:

Although I had some errors starting sage-mode -
https://bitbucket.org/gvol/sage-mode/issue/29/symbols-value-as-variable-is-void-comint- I hope restoring it's buffer will work now

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-27130448
.

[codekingplusplus]

I didn't finish sending the message; here is my ideal workgroup settings in
case you happen to think of better ways to implement these things rather
than blindly going about it.

WG1:
window1: TODO list with org-mode
window2: ielm REPL/eshell
window3: python code
window4: python interpreter

WG2:
window1: TODO list with org-mode
window2: eventually SAGE but oh well for right now.
window3: lisp code
window4: CL-REPL

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Mon, Oct 28, 2013 at 5:50 PM, Steve Styer [email protected] wrote:

Sergey,

I can see that Sage would like to work, but I am having problems with it
too. It hangs on "Sent python-eldoc-setup-code" When it freezes there it
stops emacs from loading anything else. I guess there is nothing we can do
about that...

Other than that it seems to work good, my only issue is that the CL-REPL
chooses a random window to open in each time (this does not happen with the
python interpreter -- as the python interpreter always opens in the same
window in which I save my session). Recall that I split my emacs screen
into 4 windows.

One request: Is it possible to specify via command line which workgroup I
want to open? Right now I have two workgroups. I use one for work related
tasks, and the other for math.

WG1:

Thanks for all the good work :)

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Fri, Oct 25, 2013 at 6:21 PM, Sergey Pashinin <[email protected]

wrote:

Although I had some errors starting sage-mode -
https://bitbucket.org/gvol/sage-mode/issue/29/symbols-value-as-variable-is-void-comint- I hope restoring it's buffer will work now

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-27130448
.

[codekingplusplus]

Take your time :) and sorry for blowing up your inbox...

On Mon, Oct 28, 2013 at 5:54 PM, Steve Styer [email protected] wrote:

I didn't finish sending the message; here is my ideal workgroup settings
in case you happen to think of better ways to implement these things rather
than blindly going about it.

WG1:
window1: TODO list with org-mode
window2: ielm REPL/eshell
window3: python code
window4: python interpreter

WG2:
window1: TODO list with org-mode
window2: eventually SAGE but oh well for right now.
window3: lisp code
window4: CL-REPL

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Mon, Oct 28, 2013 at 5:50 PM, Steve Styer [email protected] wrote:

Sergey,

I can see that Sage would like to work, but I am having problems with it
too. It hangs on "Sent python-eldoc-setup-code" When it freezes there
it stops emacs from loading anything else. I guess there is nothing we can
do about that...

Other than that it seems to work good, my only issue is that the CL-REPL
chooses a random window to open in each time (this does not happen with the
python interpreter -- as the python interpreter always opens in the same
window in which I save my session). Recall that I split my emacs screen
into 4 windows.

One request: Is it possible to specify via command line which workgroup I
want to open? Right now I have two workgroups. I use one for work related
tasks, and the other for math.

WG1:

Thanks for all the good work :)

-Steven Styer

Penn State University -- Class of 2014
BS Mathematics and Computer Science

On Fri, Oct 25, 2013 at 6:21 PM, Sergey Pashinin <
[email protected]> wrote:

Although I had some errors starting sage-mode -
https://bitbucket.org/gvol/sage-mode/issue/29/symbols-value-as-variable-is-void-comint- I hope restoring it's buffer will work now

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-27130448
.

[pashinin]

Is it possible to specify via command line which workgroup I want to open?

I'll try to implement it now. Create new requests - no need to have 1 big page for everything.

[pashinin]

Now you can set wg-open-this-wg variable to a WG name you want to open on start.