unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: "lein repl" malfunctions in Emacs (24.3.1) subprocess?
Date: Wed, 15 Apr 2015 23:55:33 +0200	[thread overview]
Message-ID: <87iocxukdm.fsf@zigzag.favinet> (raw)
In-Reply-To: <83bnircu3y.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Apr 2015 05:38:09 +0300")

[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]

() Eli Zaretskii <eliz@gnu.org>
() Tue, 14 Apr 2015 05:38:09 +0300

   Likely a buffering issue.  Emacs on Windows runs subprocesses
   via a pipe, and many programs then buffer their stdout fully,
   unlike line buffering they use when run from a shell prompt.

   If "lein repl", whatever that is, has an option to control
   buffering, or there's a variable you can set or command you
   can issue to that effect inside "lein repl", they will likely
   fix the problem.

Another possible weirdness is EOL convention.  But anyway...

You found a solution in ‘cider-jack-in’.  Why don't you examine
its source code, examine the ‘M-x shell’ source code and post
the conceptual diff?  (If not you, then Someone ought to do it.)

source but no reading of it: we are blind.
reading of source but no understanding: we are dumb.
understanding of one but not of many: we are alone.
how funny the universe allows us to say "we" are "alone".  :-D

-- 
Thien-Thi Nguyen -----------------------------------------------
  (if you're human and you know it) read my lisp:
    (defun responsep (type via)
      (case type
        (technical (eq 'mailing-list via))
        ...))
---------------------------------------------- GPG key: 4C807502

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2015-04-15 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 21:23 "lein repl" malfunctions in Emacs (24.3.1) subprocess? cohagan
2015-04-13 21:47 ` cohagan
2015-04-14  2:38 ` Eli Zaretskii
2015-04-15 21:55   ` Thien-Thi Nguyen [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=87iocxukdm.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).