all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: uLive System User <nyc4bos@aol.com>
Cc: 26310@debbugs.gnu.org
Subject: bug#26310: 25.1; Emacsclient to emacs --daemon frame/connection error
Date: Sat, 15 Apr 2017 10:29:34 -0400	[thread overview]
Message-ID: <87wpalsq0h.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87d1ce1hfb.fsf@aol.com> (uLive System User's message of "Fri, 14 Apr 2017 23:24:56 -0400")

tags 26310 fixed
close 26310 25.2
quit

uLive System User <nyc4bos@aol.com> writes:

> npostavs@users.sourceforge.net writes:
>
>> Live System User <nyc4bos@aol.com> writes:
>>>
>>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>>>   isearch-done(t)
>>>   isearch-cancel()
>>
>> Ah, that one.  This should be fixed already in 25.2, since #21091
>> "`isearch-done' called before `isearch-update' raises wrong-type-arg
>> error" was fixed.
>
>   I eval'ed your patched version of isearch.el into my Emacs daemon
>   and "emacsclient <file>" started working again, so thank you for
>   the fix.

Thanks for confirming.
   
>>
>> Do you happen to know how you got into this state though?  That
>> isearch-cancel is being called at all might be a bug in itself, although
>> I never found out how to reproduce it...
>
>   I don't recall what I was doing specifically.  I keep a long-running
>   Emacs daemon around and use emacsclient to connect to it regularly
>   to edit files and update my Gnu ELPA packages.

Yeah, the problem is that you wouldn't notice the state change
immediately, makes it pretty much impossible to catch this...






      reply	other threads:[~2017-04-15 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 14:31 bug#26310: 25.1; Emacsclient to emacs --daemon frame/connection error Live System User
2017-03-31  1:26 ` npostavs
2017-03-31  7:51   ` Live System User
2017-04-01  3:50     ` npostavs
2017-04-15  3:24       ` uLive System User
2017-04-15 14:29         ` npostavs [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

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

  git send-email \
    --in-reply-to=87wpalsq0h.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=26310@debbugs.gnu.org \
    --cc=nyc4bos@aol.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.