all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Jude DaShiell <jdashiel@panix.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: report-bug is also broken in emacs
Date: Sun, 5 Jul 2015 23:05:13 +0300	[thread overview]
Message-ID: <55998DF9.3090304@yandex.ru> (raw)
In-Reply-To: <alpine.NEB.2.11.1507051554540.25418@panix1.panix.com>

On 07/05/2015 10:57 PM, Jude DaShiell wrote:
> There is a script command in Linux.  When it works, it captures
> everything that goes to stdin stdout and stderr and saves that in a file
> usually called typescript.  Anything happening on a linux terminal
> visible to the user and what goes to stdout gets put in the typescript
> file.  The man script command should explain better than I'm doing here
> for you.

Thanks. Maybe someone else can look at it and tell if something specific 
looks wrong.

In the meantime, I recommend starting with 'emacs -Q'.



  reply	other threads:[~2015-07-05 20:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05 17:07 report-bug is also broken in emacs Jude DaShiell
2015-07-05 17:20 ` Dmitry Gutov
2015-07-05 17:30   ` Jude DaShiell
2015-07-05 17:37     ` Óscar Fuentes
2015-07-05 17:25 ` Óscar Fuentes
2015-07-05 18:59   ` Jude DaShiell
2015-07-05 19:06     ` Dmitry Gutov
2015-07-05 19:09       ` Jude DaShiell
2015-07-05 21:41         ` Drew Adams
     [not found]       ` <alpine.NEB.2.11.1507051519230.12588@panix2.panix.com>
2015-07-05 19:41         ` Dmitry Gutov
2015-07-05 19:57           ` Jude DaShiell
2015-07-05 20:05             ` Dmitry Gutov [this message]
     [not found]           ` <mailman.6396.1436126271.904.help-gnu-emacs@gnu.org>
2015-07-06  1:39             ` Dan Espen
2015-07-05 20:02     ` Óscar Fuentes
2015-07-06  3:31       ` Jude DaShiell

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

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

  git send-email \
    --in-reply-to=55998DF9.3090304@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jdashiel@panix.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.