all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gijs Hillenius <gijs@hillenius.net>
To: help-gnu-emacs@gnu.org
Subject: Re: auto-fill in message mode filling with prefix "> "
Date: Wed, 03 Jan 2018 10:16:23 +0100	[thread overview]
Message-ID: <87zi5v8fq0.fsf@hillenius.net> (raw)
In-Reply-To: <mailman.6710.1514910241.27995.help-gnu-emacs@gnu.org> (Eric S. Fraga's message of "Tue, 02 Jan 2018 16:23:31 +0000")

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

On  2 Jan 2018, Eric S. Fraga wrote:

> Hello,
>
> I use emacs snapshot on Debian.  Recently, but cannot say when
> exactly, my email composition has started behaving strangely with
> respect to auto-fill mode.  Specifically, if I'm responding to an
> email, as I type, long lines get auto-filled with "> " as the prefix.
> The first line of the paragraph does *not* start with "> " and I
> usually have at least one blank line between the paragraph I am typing
> and any included text from the original email.
>
> I have searched my configuration for anything that would affect this
> but I have nothing.  When it comes to auto-fill, I've left everything
> as default as far as I can tell.
>
> Any suggestions on how to track this down would be welcome.  

I'm using Emacs25 and Emacs-Snapshot on Debian. My emacs init loads
'Trivial Cite' (TC), and I do *not* experience this issue.

TC is in Debian's emacs-goodies-el. Perhaps a comparison of TC and the
Emacs efault will turn up a clue.

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

       reply	other threads:[~2018-01-03  9:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6710.1514910241.27995.help-gnu-emacs@gnu.org>
2018-01-03  9:16 ` Gijs Hillenius [this message]
2018-01-03 17:07   ` auto-fill in message mode filling with prefix "> " Eric S Fraga
     [not found]   ` <mailman.6775.1514999293.27995.help-gnu-emacs@gnu.org>
2018-01-03 17:55     ` HASM
2018-01-03 19:26       ` Alan Mackenzie
2018-01-03 20:42         ` HASM
2018-01-03 22:23       ` Stefan Monnier
     [not found]       ` <mailman.6785.1515018235.27995.help-gnu-emacs@gnu.org>
2018-01-04  2:24         ` HASM
2018-01-04 18:41           ` Stefan Monnier
     [not found] <mailman.6778.1515010834.27995.help-gnu-emacs@gnu.org>
2018-01-03 20:43 ` HASM
2018-01-03 20:53   ` Emanuel Berg
2018-01-02 16:23 Eric S Fraga
2018-01-02 16:34 ` Eric Abrahamsen
2018-01-02 16:43   ` Eli Zaretskii
2018-01-02 16:46     ` Eric Abrahamsen
2018-01-02 17:01     ` Eric S Fraga
2018-01-02 16:47   ` Eric S Fraga
     [not found]   ` <mailman.6713.1514911411.27995.help-gnu-emacs@gnu.org>
2018-01-02 18:38     ` HASM
2018-01-02 18:44       ` Eric S Fraga
     [not found]       ` <mailman.6724.1514918672.27995.help-gnu-emacs@gnu.org>
2018-01-03  1:29         ` HASM
2018-01-03 20:20           ` Robert Thorpe
2018-01-02 17:46 ` Narendra Joshi
2018-01-02 18:14   ` Eric S Fraga

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=87zi5v8fq0.fsf@hillenius.net \
    --to=gijs@hillenius.net \
    --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.
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.