On Mon, Sep 23, 2019 at 04:44:12PM -0600, Jesse Gibbons wrote:
> I need spacemacs for a class, but I want to keep my emacs settings, so I
> setup a script as described in the FAQ to separate emacs from spacemacs. The
> script sets HOME to $HOME/spacemacs and calls emacs. It appears that guix
> reca
On Mon, Jun 17, 2019 at 10:03:20AM -0700, John Soo wrote:
>Sorry this is so confusing. Let me know if I’m missed something since
>I’ve been half-following this thread. I think what you may want to do
>is use the sudoers-file field when specifying your operating system
>rather than u
On Mon, Jun 17, 2019 at 07:34:46AM -0700, Quiliro's lists wrote:
> El 2019-06-17 02:17, Andreas Enge escribió:
> > maybe my reply is off-topic and does not solve your problem, but to just
> > give sudoer capabilities to a user, it is enough to add them to the "wheel"
> > group in the system declara
On Mon, Jun 17, 2019 at 09:53:46AM +0200, Hartmut Goebel wrote:
> Try
>
> VISUAL=/path/tp/my/editor visudo
>
> See the man-page for details
Nope, same error:
$ VISUAL=~/.guix-profile/bin/vim visudo -f ~/etc/guix/config.scm
visudo: no editor found (editor path = /usr/bin/vi)
It appears /usr/bin/v
On Sun, Jun 16, 2019 at 04:08:06PM -0700, Quiliro's lists wrote:
> El 2019-06-16 09:30, Jeff Bauer escribió:
> > On Sat, Jun 15, 2019 at 07:27:57PM -0700, Quiliro's lists wrote:
> >> Regarding the EDITOR variable, if Guix is the installer of the needed
> >>
Thanks to support on #guix irc, I was able to get i3lock
working. After installing the package, i3lock would not
accept my login password. It was suggested that I add
to my config.scm:
(screen-locker-service i3lock "i3lock")
However, I still wasn't able to unlock my screen. Next
suggestion was
On Sat, Jun 15, 2019 at 07:27:57PM -0700, Quiliro's lists wrote:
> Regarding the EDITOR variable, if Guix is the installer of the needed
> editor it is the only situation when this regards to Guix.
>
> Would you please clarify your issue?
Issue clarified up-thread:
https://lists.gnu.org/archive/h
On Sat, Jun 15, 2019 at 07:27:57PM -0700, Quiliro's lists wrote:
> Regarding the EDITOR variable, if Guix is the installer of the needed
> editor it is the only situation when this regards to Guix.
>
> Would you please clarify your issue?
Issue clarified up-thread:
https://lists.gnu.org/archive/h
Thanks to support on #guix irc, I was able to get i3lock
working. After installing the package, i3lock would not
accept my login password. It was suggested that I add
to my config.scm:
(screen-locker-service i3lock "i3lock")
However, I still wasn't able to unlock my screen. Next
suggestion was
On Fri, Jun 14, 2019 at 03:21:33PM +0200, Tobias Geerinckx-Rice wrote:
> (operating-system
>…
>(sudoers-file
> (local-file "sudoers")) ; relative to this file
>…)
Thanks. And as a note to myself to RTFM:
https://www.gnu.org/software/guix/manual/en/html_node/Using-the-Configurat
I've been trying unsuccessfully to make changes to
/etc/sudoers. I used visudo by creating a symlink
to /usr/bin/vi (because visudo ignores EDITOR), but
the changes aren't permanent. What am I missing?
-Jeff
I've installed emacs 26.2 from the guix package
onto a foreign debian distro. Mostly everything
appears to work fine, but play-sound-file causes:
"No usable sound device driver found"
I've installed alsa-lib and aplay -l produces:
card 1: PCH [HDA Intel PCH], device 0: ALC283 Analog [ALC283 Ana
I've put the following in my .profile:
GUIX_PROFILE="$HOME/.guix-profile"
if [ -d $GUIX_PROFILE ] || [ -h $GUIX_PROFILE ] ; then
export GUIX_PROFILE
export GUIX_LOCPATH=$GUIX_PROFILE/lib/locale/
source $GUIX_PROFILE/etc/profile
fi
I have it set up this way so my .profile is portable
b
13 matches
Mail list logo