Gnus development mailing list
 help / color / mirror / Atom feed
From: Martin <parozusa@web.de>
To: ding@gnus.org
Subject: Re: lost the ability to copy
Date: Wed, 03 Sep 2014 09:21:36 +0200	[thread overview]
Message-ID: <82ha0pf9tr.fsf@web.de> (raw)
In-Reply-To: <87egvu1suq.fsf@skimble.plus.com>



Sharon Kimble writes:

> When I am replying to a post now, be it email or newsgroup, if I use
> 'Post -> Wide reply and yank', or just 'Post -> Wide reply', neither of
> them give me a copy of the original post.
>
> How then can I regain this please?
>
> Thanks
> Sharon.

Hi,

both commands work as specified here (see below).

Martin

  Gnus v5.13
  GNU Emacs 24.3.93.1 (i686-pc-mingw32) of 2014-08-15 on LEG570

  -------
  <menu-bar> <Post> <Wide reply> runs the command
  gnus-summary-wide-reply, which is an interactive autoloaded compiled
  Lisp function in `gnus-msg.el'.

  It is bound to S w, <menu-bar> <Post> <Wide reply>.

  (gnus-summary-wide-reply &optional YANK)

  Start composing a wide reply mail to the current message.
  If prefix argument YANK is non-nil, the original article is yanked
  automatically.


  -------
  <menu-bar> <Post> <Wide reply and yank> runs the command
  gnus-summary-wide-reply-with-original, which is an interactive
  autoloaded compiled Lisp function in `gnus-msg.el'.

  It is bound to S W, <menu-bar> <Post> <Wide reply and yank>.

  (gnus-summary-wide-reply-with-original N)

  Start composing a wide reply mail to the current message.
  The original article will be yanked.
  Uses the process/prefix convention.

  [back]




      parent reply	other threads:[~2014-09-03  7:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  5:42 Sharon Kimble
2014-09-02  7:47 ` Alberto Luaces
2014-09-03  7:21 ` Martin [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=82ha0pf9tr.fsf@web.de \
    --to=parozusa@web.de \
    --cc=ding@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).