From: MON KEY <monkey@sandpframing.com>
To: 7503@debbugs.gnu.org
Cc: mje@inducks.org, schwab@linux-m68k.org, sdl.web@gmail.com
Subject: bug#7503: copy-and-insert-previous-line
Date: Sun, 28 Nov 2010 16:05:34 -0500 [thread overview]
Message-ID: <AANLkTiktvxKX5AihQ0yK62ve6u13wrZ-cf0cpjGNkdd1@mail.gmail.com> (raw)
In-Reply-To: <4CF22EA9.3020207@inducks.org>
I think such differences is the reason why such commands are not
very good candidates for inclusion in Emacs: there are so many
different commands that do something along these lines, that
adding them all would not make much sense.
FWIW following is my more generalized take on Andreas' and Mads' versions.
This one:
- Doesn't step on the kill-ring;
- Has option to keep/omit text-props;
- inserts only when asked to do so:
;;; <Timestamp: #{2010-11-28T12:10:07-05:00Z}#{10477} - by MON>
(defun line-previous-duplicate (&optional keep-props insrtp intrp)
"Return content of previous line.
When optional arg KEEP-PROPS is non-nil return value is as if by
`buffer-substring'. Default is as if by `buffer-substring-no-properties'.
When optional arg INSRTP is non-nil or called-interactively, insert return value
at point. Does not move point."
(interactive "*i\ni\np")
(save-excursion
(let ((lpd-psns `(,(progn (forward-line -1) (point)) .
,(progn (forward-line 1) (point)))))
(set (or (and intrp (quote intrp))
(and insrtp (quote insrtp))
(and (set (quote intrp) (quote insrtp))
(quote insrtp)))
(or (and keep-props
(buffer-substring (car lpd-psns) (cdr lpd-psns)))
(buffer-substring-no-properties
(car lpd-psns) (cdr lpd-psns)))))
(or (and (not (eq intrp 'insrtp))
(stringp insrtp)
(insert insrtp))
(and intrp
(stringp intrp)
(insert intrp))
insrtp)))
--
/s_P\
prev parent reply other threads:[~2010-11-28 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 10:27 bug#7503: copy-and-insert-previous-line Mads Jensen
2010-11-28 11:10 ` Andreas Schwab
2010-11-28 12:56 ` Leo
2010-11-28 13:37 ` Eli Zaretskii
2010-11-28 14:13 ` martin rudalics
2010-11-28 14:28 ` Eli Zaretskii
2010-11-28 15:04 ` martin rudalics
2010-11-28 15:44 ` Eli Zaretskii
2010-11-28 16:11 ` martin rudalics
2010-11-28 14:32 ` Mads Jensen
2010-11-28 18:57 ` Stefan Monnier
2010-11-28 21:05 ` MON KEY [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
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=AANLkTiktvxKX5AihQ0yK62ve6u13wrZ-cf0cpjGNkdd1@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=7503@debbugs.gnu.org \
--cc=mje@inducks.org \
--cc=schwab@linux-m68k.org \
--cc=sdl.web@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).