unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bradley Haggerty <bradigger@gmail.com>
To: 34616@debbugs.gnu.org
Subject: bug#34616: neovim segfaults
Date: Tue, 5 Mar 2019 19:53:41 +0000	[thread overview]
Message-ID: <CABGw91dAgDbZgq3SgmZ4wOXVbwZj-trE4oRO=OsCfv5cQTm8Sg@mail.gmail.com> (raw)
In-Reply-To: <5cacf4b49b42b6c8f29ea14772ac4068@lepiller.eu>

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

Jumping in here to share some of my own info as I'm having the same issue.

brad@kazuki:~/ > nvim
zsh: segmentation fault  nvim

I've got neovim installed in the system profile (so root has a comfortable
editor instead of just nano)
guix (GNU Guix) d22d246a256814784dfb03437949bdc2efd746a5
brad@kazuki:~/ > echo $TERM
screen-256color
Here is my $TERM. I am running inside tmux using termite as my terminal
emulator.
For the record I get the same segmentation fault outside of tmux using the
same terminal emulator.
brad@kazuki:~/ > echo $TERM
xterm-termite

I tried the guix environment --container command that Ricardo shared and in
that instance nvim works for me in tmux just fine as well. If there's more
info about my environment I can share to help track down the issue, please
let me know.

[-- Attachment #2: Type: text/html, Size: 1033 bytes --]

  parent reply	other threads:[~2019-03-05 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 13:06 bug#34616: neovim segfaults Julien Lepiller
2019-02-22 15:06 ` Ricardo Wurmus
2019-02-22 15:13   ` Julien Lepiller
2019-02-22 15:57     ` Ricardo Wurmus
2019-02-22 16:35       ` Julien Lepiller
2019-02-22 17:11         ` Ricardo Wurmus
2019-02-24  9:02           ` Efraim Flashner
2019-03-01 16:31             ` Ricardo Wurmus
2019-03-05 19:53 ` Bradley Haggerty [this message]
     [not found] <CAE4v=pg1YHwn4_xqJCpARYyn2qY1qK=o_aX6zB2fsGLN6je53A@mail.gmail.com>
2019-03-07 10:25 ` Gábor Boskovits

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='CABGw91dAgDbZgq3SgmZ4wOXVbwZj-trE4oRO=OsCfv5cQTm8Sg@mail.gmail.com' \
    --to=bradigger@gmail.com \
    --cc=34616@debbugs.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. 
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).