From: Dmitrii Kashin <freehck@freehck.ru>
To: info-gnus-english@gnu.org
Subject: Re: Loss of first paragraph on fill and reply
Date: Tue, 12 Nov 2013 05:58:10 +0400 [thread overview]
Message-ID: <871u2mv0st.fsf@lpt00.freehck.ru> (raw)
In-Reply-To: <87ppq6a16y.fsf@nl106-137-194.student.uu.se>
[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]
Emanuel Berg <embe8573@student.uu.se> writes:
> Dmitrii Kashin <freehck@freehck.ru> writes:
>
>> Easily. Move your gnus-rc file (~/.gnus) somewhere,
>> start emacs with -q (not -Q) flag. Run `gnus`
>> function. Then use B key [1] to browse any nntp server
>> you want. And then try to answer somebody.
>
> You are absolutely right, neither of these issues are
> there when I start Emacs and Gnus the way you suggest,
> i.e., without my configuration/extension.
Well, this is the good news. Thus, a problem exists somewhere inside
your configuration.
You have a lot of configuration files. Try now to load some of them in
order to detect which one does contain problem code.
I suppose it could be .emacs-message or .emacs-gnus.
PS: Of course, the most sane way to detect problem is to watch some kind
of backtrace when you are in the buffer for message composing. But to be
fair I'm still unable to debug such a right way.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2013-11-12 1:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 14:14 Emanuel Berg
2013-11-10 18:23 ` Dmitrii Kashin
[not found] ` <mailman.5731.1384107817.10748.info-gnus-english@gnu.org>
2013-11-10 21:14 ` Emanuel Berg
2013-11-10 22:34 ` Dmitrii Kashin
[not found] ` <mailman.5771.1384122902.10748.info-gnus-english@gnu.org>
2013-11-12 0:54 ` Emanuel Berg
2013-11-12 1:58 ` Dmitrii Kashin [this message]
[not found] ` <mailman.5851.1384221526.10748.info-gnus-english@gnu.org>
2013-11-12 2:44 ` Emanuel Berg
2013-11-12 3:21 ` Emanuel Berg
2013-11-12 6:57 ` Dmitrii Kashin
[not found] ` <mailman.5865.1384239506.10748.info-gnus-english@gnu.org>
2013-11-12 21:09 ` Emanuel Berg
2013-11-13 7:08 ` Dmitrii Kashin
[not found] ` <mailman.5948.1384326540.10748.info-gnus-english@gnu.org>
2013-11-13 19:47 ` Emanuel Berg
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=871u2mv0st.fsf@lpt00.freehck.ru \
--to=freehck@freehck.ru \
--cc=info-gnus-english@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 NNTP newsgroup(s).