From: Caleb Herbert <csh@bluehome.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Application Setup on Trisquel
Date: Thu, 26 Oct 2017 15:05:47 -0500 [thread overview]
Message-ID: <1509048347.6090.10.camel@leela> (raw)
In-Reply-To: <87po99g5k7.fsf@gnu.org>
On Thu, 2017-10-26 at 10:52 -0700, Ludovic Courtès wrote:
> "Caleb Herbert" <csh@bluehome.net> skribis:
> > I had to comment those lines in /etc/profile because Trisquel's
> > display manager would return me to the login screen after entering my
> > password.
The errors happened even when I commented the lines. I think the
whole .profile was just written wrong. It came from my Slackware
backup.
> Does ~/.xsession-errors contain hints as to why this happened?
I had to delete the entire .profile so my login works. .xsession-errors
now says nothing interesting, AFAIK:
cal@leela:~$ cat .xsession-errors
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
GNOME's Alt+F2 launcher still doesn't know where Emacs is, but the main
menu does.
> I’d probably move “source $HOME/.guix-profile/etc/profile” to
> ~/.bash_profile, though.
That's what I've done. I think I'm going to keep it this way.
> But that’s really a shell question more than a Guix question, I think.
Sorry. It's hard to figure some things out sometimes.
> HTH!
What does this mean, anyway?
next prev parent reply other threads:[~2017-10-26 20:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 18:12 Application Setup on Trisquel Caleb Herbert
2017-10-24 21:16 ` Ludovic Courtès
2017-10-24 22:04 ` Caleb Herbert
2017-10-26 17:54 ` Ludovic Courtès
2017-10-27 1:02 ` Chris Marusich
2017-10-24 23:33 ` Caleb Herbert
2017-10-24 23:44 ` Caleb Herbert
2017-10-26 17:52 ` Ludovic Courtès
2017-10-26 20:05 ` Caleb Herbert [this message]
2017-10-25 0:36 ` Mikhail Kryshen
2017-10-26 17:53 ` Ludovic Courtès
2017-10-27 3:29 ` Caleb Herbert
2017-11-08 6:39 ` Caleb Herbert
2017-11-09 21:05 ` Chris Marusich
2017-11-10 21:29 ` Caleb Herbert
2017-11-12 14:55 ` Adonay Felipe Nogueira
2017-11-12 17:09 ` Adonay Felipe Nogueira
2017-11-12 13:02 ` Adonay Felipe Nogueira
2017-11-02 2:59 ` Mark H Weaver
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=1509048347.6090.10.camel@leela \
--to=csh@bluehome.net \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
/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.
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).