sage --dev commit keeps using nano!

59 views
Skip to first unread message

Dima Pasechnik

unread,
Dec 19, 2013, 9:18:47 AM12/19/13
to sage...@googlegroups.com
while
$ sage --git var GIT_EDITOR
vim
and
$ git var GIT_EDITOR
vim
(and vim is not an alias to nano)
I still get
sage --dev commit
popping nano for me...

Any clues why?
(This is on Debian 7, in case...)

Thanks
Dima

Nathann Cohen

unread,
Dec 19, 2013, 9:21:32 AM12/19/13
to sage...@googlegroups.com
Hmmmmm... Weird. Is EDITOR also set to vim ?

Nathann


Dima

--
You received this message because you are subscribed to the Google Groups "sage-git" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-git+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Dima Pasechnik

unread,
Dec 19, 2013, 11:33:01 AM12/19/13
to sage...@googlegroups.com
On 2013-12-19, Nathann Cohen <nathan...@gmail.com> wrote:
> Hmmmmm... Weird. Is EDITOR also set to vim ?
it's not set.
Also,
sage --git commit
and
git commit
behave just fine.
So this is a 'sage --dev' "feature", but I can't seem to find
the place in the code where this happens...

Dima

Volker Braun

unread,
Dec 19, 2013, 11:39:17 AM12/19/13
to sage...@googlegroups.com
The dev script uses EDITOR, if it is not set it uses nano.

Dima Pasechnik

unread,
Dec 19, 2013, 11:36:51 AM12/19/13
to sage...@googlegroups.com
On 2013-12-19, Dima Pasechnik <dim...@gmail.com> wrote:
> On 2013-12-19, Nathann Cohen <nathan...@gmail.com> wrote:
>> Hmmmmm... Weird. Is EDITOR also set to vim ?
> it's not set.
In fact, setting EDITOR to vim makes it work
as it should. But this is insane - git behaviour should be
controlled by git settings, not but some irrelevant variable...

Dima

P Purkayastha

unread,
Dec 20, 2013, 3:56:15 AM12/20/13
to sage...@googlegroups.com
EDITOR is a system level setting. Everything should first look at EDITOR
and then look at individual application setting.

basu.

P Purkayastha

unread,
Dec 20, 2013, 3:58:08 AM12/20/13
to sage...@googlegroups.com
Sorry, I meant the other way round. If the setting is not specified in
the individual application, then it should look at EDITOR. In case of
Sage, it should just look at EDITOR (there is no way to set an editor in
Sage as far as I know).


Ralf Hemmecke

unread,
Dec 20, 2013, 4:13:47 AM12/20/13
to sage...@googlegroups.com
> Sorry, I meant the other way round. If the setting is not specified in
> the individual application, then it should look at EDITOR.

Git tries first the environment variable GIT_EDITOR.

https://www.kernel.org/pub/software/scm/git/docs/git-var.html

Ralf

Vincent Delecroix

unread,
Dec 21, 2013, 4:16:49 AM12/21/13
to sage...@googlegroups.com
Where does point your /usr/bin/editor ?

2013/12/19, Dima Pasechnik <dim...@gmail.com>:

Dima Pasechnik

unread,
Jan 31, 2014, 4:03:59 PM1/31/14
to sage...@googlegroups.com
On 2013-12-21, Vincent Delecroix <20100.d...@gmail.com> wrote:
> Where does point your /usr/bin/editor ?
it does not exist.


Reply all
Reply to author
Forward
0 new messages