all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Shawn Presser <shawnpresser@gmail.com>
Cc: 34123@debbugs.gnu.org
Subject: bug#34123: A patch to fix reading EOF characters in non-interactive mode
Date: Mon, 21 Jan 2019 17:44:20 +0200	[thread overview]
Message-ID: <83tvi29fsb.fsf@gnu.org> (raw)
In-Reply-To: <CALtdh+-6MpLxg-h5ghmDixAEnGsz8whr2fGvJqN88EAF9h7FtA@mail.gmail.com> (message from Shawn Presser on Mon, 21 Jan 2019 02:59:36 -0600)

> From: Shawn Presser <shawnpresser@gmail.com>
> Date: Mon, 21 Jan 2019 02:59:36 -0600
> Cc: 34123@debbugs.gnu.org
> 
> Hi, just checking in. I wanted to thank you for taking the time to reply and ask about this bug. It's my first
> emacs patch and I'm not entirely sure if I'm following the process correctly here. I'd like to try answering your
> questions more succinctly.
> 
> Is there a "next step" at this point, or something that I can do to help with emacs in general?

I'm still considering the implications of your suggestion on the other
use cases.  One possible alternative would be to add a function that
will clear the error condition, and let users/Lisp programs call it.
This way, the default response to EOF will remain intact.

Perhaps someone else will chime in with opinions and ideas.

Thanks.





  reply	other threads:[~2019-01-21 15:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 10:35 bug#34123: A patch to fix reading EOF characters in non-interactive mode Shawn Presser
2019-01-18 13:25 ` Eli Zaretskii
2019-01-18 14:22   ` Shawn Presser
2019-01-18 16:03     ` Eli Zaretskii
2019-01-18 16:20       ` Shawn Presser
2019-01-18 16:29         ` Eli Zaretskii
2019-01-18 17:23           ` Shawn Presser
2019-01-20  1:22           ` Shawn Presser
2019-01-21  8:59           ` Shawn Presser
2019-01-21 15:44             ` Eli Zaretskii [this message]
2020-08-10 11:56               ` Lars Ingebrigtsen
2020-08-19 10:57                 ` Lars Ingebrigtsen
2019-06-23  0:18 ` Noam Postavsky

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=83tvi29fsb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34123@debbugs.gnu.org \
    --cc=shawnpresser@gmail.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.