bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#38273: bug#38274: emacs doesn't open files


From: Jesse Gibbons
Subject: bug#38273: bug#38274: emacs doesn't open files
Date: Tue, 19 Nov 2019 21:13:15 -0700
User-agent: Evolution 3.30.5

On Wed, 2019-11-20 at 06:20 +0900, Maxim Cournoyer wrote:
> Hello Jesse,
> 
> Jesse Gibbons <address@hidden> writes:
> 
> > On Tue, 2019-11-19 at 08:35 -0700, Jesse Gibbons wrote:
> > > guix describe :
> > > Generation 139    Nov 19 2019 08:11:32    (current)
> > >   guix 7b40d59
> > >     repository URL: https://git.savannah.gnu.org/git/guix.git
> > >     branch: master
> > >     commit: 7b40d59114e1462d6d8140f325a66b12e91db667
> > > 
> > > emacs --version :
> > > GNU Emacs 26.3
> > > Copyright (C) 2019 Free Software Foundation, Inc.
> > > GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> > > You may redistribute copies of GNU Emacs
> > > under the terms of the GNU General Public License.
> > > For more information about these matters, see the file named COPYING.
> > > 
> > > When I launch emacs from the command line, I get the following
> > > message:
> > > split-string: Wrong type argument: stringp, nil
> > > 
> > > As a result, when I try `EDITOR=emacs guix edit hello` it doesn't
> > > work.
> > > I can confirm this is not a problem with guix edit, because when
> > > EDITOR=vim
> > > it opens the package in vim.
> > > 
> > > (Joke about guix turning to the dark side goes here.)
> > > 
> > > Since I do not know if it is a problem with guix or emacs, I'm
> > > starting
> > > with
> > > guix. It could be related to bug#38261
> > > 
> > > 
> > > 
> > > 
> > I guess this was fixed for me by restarting my computer.
> > 
> > (joke about "turning it off and back on" working goes here)
> 
> It seems the EMACSLOADPATH was not defined in your environment.  
Ok.
> Do you use Emacs in your main user profile?
Yes.
> How did this happen? Did you simply 'guix pull' and 'guix upgrade -u .'
> said profile?
"guix pull && guix upgrade" 
> 
> In all cases, simply login out and back in should probably have fixed
> the issue (instead of a reboot).
As I recall, I turned it off, commuted to a class, and turned it back on.
> 
> Thanks for the report!
> 
> Maxim






reply via email to

[Prev in Thread] Current Thread [Next in Thread]