all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: yyoncho <yyoncho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38561@debbugs.gnu.org
Subject: bug#38561: 27.0.50; Feature request: expose buffer size setting for process filters
Date: Sat, 21 Dec 2019 21:30:15 +0200	[thread overview]
Message-ID: <CACCVLQXWp6waMWjhHfbfyowWp8=sp8gJxRyX2jsgqCsZFCrw2Q@mail.gmail.com> (raw)
In-Reply-To: <83h81tzgca.fsf@gnu.org>

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

I think that it will be fairly common (e. g. everyone using lsp-mode)
will have to use that setting. I am afraid that even if I choose option 1
the distributions like spacemacs/doom will set it globally(because they
are allowed to be opinionated).

When you create a process you provide a bunch of settings(e. g.
:connection-type, :filter, :no-query). Can we make another property for
the read max size?

Thanks,
Ivan

On Sat, Dec 21, 2019 at 8:25 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > > 1. Document it in lsp-mode's readme
> > > 2. Override it with a setting in lsp-mode with a bigger value.
> > >
> > > Both have clear advantages and disadvantages. Can you advise?
> >
> > I'd suggest the former, because if lsp-mode sets the value, it will
> > affect the entire Emacs session.
> >
> > If lsp-mode uses accept-process-output, it could bind the variable
> > inside the form which calls accept-process-output.
>
> 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?).
>

[-- Attachment #2: Type: text/html, Size: 1708 bytes --]

  reply	other threads:[~2019-12-21 19:30 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 [this message]
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

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='CACCVLQXWp6waMWjhHfbfyowWp8=sp8gJxRyX2jsgqCsZFCrw2Q@mail.gmail.com' \
    --to=yyoncho@gmail.com \
    --cc=38561@debbugs.gnu.org \
    --cc=eliz@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.
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.