all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 38561@debbugs.gnu.org, yyoncho@gmail.com
Subject: bug#38561: 27.0.50; Feature request: expose buffer size setting for process filters
Date: Sun, 22 Dec 2019 19:25:05 +0200	[thread overview]
Message-ID: <83zhfkxoge.fsf@gnu.org> (raw)
In-Reply-To: <a3fb65a5-b4d1-5d50-ff06-7990b6d908cb@yandex.ru> (message from Dmitry Gutov on Sun, 22 Dec 2019 16:23:13 +0200)

> Cc: 38561@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 22 Dec 2019 16:23:13 +0200
> 
> On 21.12.2019 20:25, Eli Zaretskii wrote:
> > Btw, my assumption was that the value will have to be changed from
> > default only in very rare situations.  If this is not the case, we
> > might indeed want that to be a parameter at process creation time (I
> > don't think we have process-local variables, do we?).
> 
> Could the process use the buffer-local value of this variable?

It didn't work for Ivan, I'm not yet sure why.  Feel free to
investigate.

> Or, alternatively, use the value this variable had at the point of 
> process's creation. Then the caller could just temporarily bind it.

That's impossible without saving the value in the process object.





      reply	other threads:[~2019-12-22 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 17:17 bug#38561: 27.0.50; Feature request: expose buffer size setting for process filters yyoncho
2019-12-10 17:25 ` yyoncho
2019-12-21  8:49   ` Eli Zaretskii
2019-12-21 14:43     ` yyoncho
2019-12-21 17:47       ` Eli Zaretskii
2019-12-21 18:25         ` Eli Zaretskii
2019-12-21 19:30           ` yyoncho
2019-12-21 19:36             ` Eli Zaretskii
2019-12-21 19:59               ` yyoncho
2019-12-22 14:23           ` Dmitry Gutov
2019-12-22 17:25             ` Eli Zaretskii [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=83zhfkxoge.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38561@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=yyoncho@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.