unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 38273-done@debbugs.gnu.org
Subject: bug#38273: bug#38274: emacs doesn't open files
Date: Tue, 19 Nov 2019 21:13:15 -0700	[thread overview]
Message-ID: <52cfff32af03af0c8526072784215234fd2a6eb7.camel@gmail.com> (raw)
In-Reply-To: <878sobwoky.fsf@gmail.com>

On Wed, 2019-11-20 at 06:20 +0900, Maxim Cournoyer wrote:
> Hello Jesse,
> 
> Jesse Gibbons <jgibbons2357@gmail.com> 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	other threads:[~2019-11-20  4:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 15:35 bug#38273: emacs doesn't open files Jesse Gibbons
2019-11-19 16:16 ` zimoun
2019-11-19 21:51   ` Maxim Cournoyer
2019-11-20  4:08     ` Jesse Gibbons
2019-11-20 17:20       ` zimoun
2019-11-20 17:19     ` zimoun
2019-11-22  3:46       ` Maxim Cournoyer
2019-11-22 13:42         ` zimoun
2019-11-19 17:07 ` bug#38274: " Jesse Gibbons
2019-11-19 21:20   ` bug#38273: " Maxim Cournoyer
2019-11-20  4:13     ` Jesse Gibbons [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52cfff32af03af0c8526072784215234fd2a6eb7.camel@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=38273-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).