unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Brad Johnson <brad@pesquared.com>
Cc: 21053 <21053@debbugs.gnu.org>
Subject: bug#21053: 24.5; emacs "-nw" option crashes in zsh brad@pesquared.com
Date: Tue, 14 Jul 2015 12:46:51 +0200	[thread overview]
Message-ID: <87k2u3c8ys.fsf@gnu.org> (raw)
In-Reply-To: <CADSjb9X4+PEK7NXCbyXzDvhBJxhpMUxVHngcoXnGG_s9viXpUg@mail.gmail.com> (Brad Johnson's message of "Tue, 14 Jul 2015 04:16:55 -0400")

Hi Brad,

I just installed oh-my-zsh but can't reproduce a crash with the emacs
plugin.  What the plugin does is defining an emacs alias which actually
calls emacsclient.  Concretely, "emacs args" will call

  emacsclient --alternate-editor "" --create-frame --no-wait args

or

  emacsclient --alternate-editor "" --no-wait args

With the plugin enabled, I get the following

  $ emacs
  emacsclient: file name or argument required
  Try `emacsclient --help' for more information

  $ emacs -nw
  emacsclient: file name or argument required
  Try `emacsclient --help' for more information

  $ emacs file
  # file is opened in existing X frame

  $ emacs -nw file
  # file is opened in existing X frame, the -nw option seems to be
  # ignored

That the -nw flag is ignored and it doesn't work with no file given can
be considered bugs of that plugin in their own respect, but at least
that doesn't crash emacs.  But I'm using a current emacs git checkout
rather than 24.5, so could you please test if the two emacsclient
commands above crash your emacs version?

Bye,
Tassilo





  reply	other threads:[~2015-07-14 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  0:36 bug#21053: 24.5; emacs "-nw" option crashes in zsh brad@pesquared.com Brad
2015-07-14  7:02 ` Tassilo Horn
2015-07-14  7:42   ` Brad Johnson
2015-07-14  8:00     ` Brad Johnson
2015-07-14  8:16       ` Brad Johnson
2015-07-14 10:46         ` Tassilo Horn [this message]
2016-12-07 18:53         ` Glenn Morris

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=87k2u3c8ys.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=21053@debbugs.gnu.org \
    --cc=brad@pesquared.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 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).