unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: drain <aeuster@gmail.com>
To: Help-gnu-emacs@gnu.org
Subject: Re: moving text from one buffer to another
Date: Fri, 18 Jan 2013 04:25:29 -0800 (PST)	[thread overview]
Message-ID: <1358511929530-275792.post@n5.nabble.com> (raw)
In-Reply-To: <86wqvayfu5.fsf@w2139spb.ru.yotateam.com>

What matters is that I am copying text from one buffer into another. At
least in terms of the aims of this function, I do not think org-mode has
any impact on the functionality.

Your suggestion helps. One of the core redundancies here is how many times
various forms of input are being copied.




--
View this message in context: http://emacs.1067599.n5.nabble.com/moving-text-from-one-buffer-to-another-tp275785p275792.html
Sent from the Emacs - Help mailing list archive at Nabble.com.



  reply	other threads:[~2013-01-18 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  8:39 moving text from one buffer to another drain
2013-01-18  9:56 ` Filipp Gunbin
2013-01-18 12:25   ` drain [this message]
2013-01-18 13:11     ` Filipp Gunbin
2013-01-18 13:25       ` drain

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1358511929530-275792.post@n5.nabble.com \
    --to=aeuster@gmail.com \
    --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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).