unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 25170@debbugs.gnu.org, felix.dick@web.de
Subject: bug#25170: 26.0.50; emacs crashes on using tramp
Date: Sun, 11 Dec 2016 20:05:44 +0200	[thread overview]
Message-ID: <8360mqe3yf.fsf@gnu.org> (raw)
In-Reply-To: <87shpua93v.fsf@gmx.de> (message from Michael Albinus on Sun, 11 Dec 2016 14:28:04 +0100)

> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Sun, 11 Dec 2016 14:28:04 +0100
> Cc: 25170@debbugs.gnu.org
> 
> > At first, i have to say that i'm sorry that I dont use the proper report-emacs-bug system, but I didn't succeed doing that.
> > It's really not easy to use this emacs bug-reporting system, and if you want everybody to be able to report bugs, the system should be simpler!
> 
> Could you pls tell us in detail what annoys you?

Yes, please.

> > Anyways, here is the Bug report, if I follow this, emacs crashes every time.
> > I use arch linux x86-64
> > If i start 'emacs -Q'
> > after 'C-x C-f' (find-file) and entering '/ssh:'
> 
> For the records, this doesn't happen for me with a todays build of git
> master:
> 
> GNU Emacs 26.0.50.17 (x86_64-pc-linux-gnu, GTK+ Version 2.24.30)
>  of 2016-12-11
> 
> I'm running Ubuntu 16.10.

I tried this on Trisquel and on MS-Windows, and couldn't reproduce
this, either.

> Could you, pls, check the instructions in etc/DEBUG how to retrieve
> better traces?

Yes, please.





      parent reply	other threads:[~2016-12-11 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11 12:21 bug#25170: 26.0.50; emacs crashes on using tramp felix.dick
2016-12-11 13:28 ` Michael Albinus
2016-12-11 13:33   ` Felix
2017-12-11 12:27     ` Michael Albinus
2016-12-11 18:05   ` Eli Zaretskii [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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=8360mqe3yf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25170@debbugs.gnu.org \
    --cc=felix.dick@web.de \
    --cc=michael.albinus@gmx.de \
    /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/emacs.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).