From: Sergey Organov <sorganov@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: Dribble buffer breakage.
Date: Mon, 08 Feb 2016 17:29:55 +0300 [thread overview]
Message-ID: <871t8ncm1o.fsf@javad.com> (raw)
In-Reply-To: <87fux6saj7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Feb 2016 15:55:08 +1100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Sergey Organov <sorganov@gmail.com> writes:
>
>> Hello,
>>
>> commit 5d7c18060995c206e8a708829fa30801885cb972
>> Author: Katsumi Yamaoka <yamaoka@jpl.org>
>> Date: Fri Jun 10 00:09:30 2011 +0000
>>
>> Improve dribble data handling.
>>
>> This commit breaks '.newsrc-dribble' buffer handling when gnus group
>> contains 'posting-style' with embedded newline characters, because of
>> newly introduced feature of 'gnus-dribble-enter' to remove /lines/
>> matching 'regexp' argument.
>>
>> Either 'posting-style' must not be part of `gnus-newsrc-alist' elements,
>> or 'posting-style' must be excluded when saving group info into the
>> dribble buffer, or 'gnus-dribble-enter' must remove entire sexp matching
>> 'regexp', not lines.
>
> I guess it could also insert things into the dribble buffer with "\n"
> instead of real newlines? They would read the same, but would make
> every dribble be on one single line...
>
> I think I'll make that change. It should be pretty trivial.
I'd rather vote for excluding 'posting-style' from dribble buffer, as,
being customisable user setting, it is always saved elsewhere. It takes
space and gives problems in dribble buffer for no reason.
--
Sergey.
prev parent reply other threads:[~2016-02-08 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wpwo4qss.fsf@javad.com>
2016-02-06 4:55 ` Lars Ingebrigtsen
2016-02-08 14:29 ` Sergey Organov [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=871t8ncm1o.fsf@javad.com \
--to=sorganov@gmail.com \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.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 NNTP newsgroup(s).