unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tak Ota <Takaaki.Ota@am.sony.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: keymap in yank-excluded-properties
Date: Fri, 30 Aug 2002 12:43:08 -0700 (PDT)	[thread overview]
Message-ID: <20020830.124308.81460907.Takaaki.Ota@am.sony.com> (raw)
In-Reply-To: <5x3ct2y2nr.fsf@kfs2.cua.dk>

26 Aug 2002 00:49:44 +0200: storm@cua.dk (Kim F. Storm) wrote:

> Perhaps a new text property `yank-function' which takes a function as value.
> 
> `yank' will look for that property on kill-ring elements and call the
> function with one argument: the string (or rectangle?) to yank.  The
> function is then responsible for inserting the string in the buffer
> and remove any unwanted properties [i.e. it is expected to do the
> actual insertion].
> 
> A table could have this property set to a function which check that 
> the string to insert is really a complete table -- and keep the 
> properties in that case [using insert] -- or remove the properties 
> otherwise [using insert-for-yank].
> 
> This is a simple, but flexible concept which may be used for other
> purposes as well; for example, text killed by a "special" function
> [e.g. kill-rectangle] may be later inserted using plain C-y by another
> special function [e.g. insert-rectangle].

I think this is a neat idea.  However, there is a discussion whether
we want `yank-function' that takes over whole `yank' operation or
`yank-insert-function' that replaces only `insert-for-yank' part of
`yank'.  `insert-for-yank' is the one that actually strips off the
undesired text properties.

I prefer later from `table.el' application point of view but the
former is more generic and flexible.  But then that flexibility
involves the relationship with command replacement which is out of the
scope of this discussion.

-Tak

  reply	other threads:[~2002-08-30 19:43 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23  0:31 keymap in yank-excluded-properties Tak Ota
2002-08-23  1:55 ` Miles Bader
2002-08-23 22:21   ` Tak Ota
2002-08-23 22:29     ` Stefan Monnier
2002-08-23 23:04       ` Tak Ota
2002-08-23  9:52 ` Kim F. Storm
2002-08-25  5:25 ` Richard Stallman
2002-08-25 22:49   ` Kim F. Storm
2002-08-30 19:43     ` Tak Ota [this message]
2002-09-01 13:14       ` Richard Stallman
2002-09-02 15:02         ` Kim F. Storm
2002-09-03 13:26           ` Richard Stallman
2002-09-03 20:36             ` Tak Ota
2002-10-23 13:53               ` Kim F. Storm
2002-10-24 20:27                 ` Tak Ota
2002-09-04  1:11           ` Miles Bader
2002-09-04  6:32             ` Juanma Barranquero
2002-09-04  8:45               ` Kim F. Storm
2002-09-04  8:02                 ` Miles Bader
2002-09-04  8:50                   ` Juanma Barranquero
2002-09-04  8:49                 ` Juanma Barranquero
2002-09-04 12:48                   ` Kim F. Storm
2002-09-04 14:10                     ` Juanma Barranquero
2002-09-04 10:34                 ` Per Abrahamsen
2002-09-04 12:35                   ` Kim F. Storm
2002-09-05  1:10                     ` Miles Bader
2002-09-05 13:18                       ` Robert J. Chassell
2002-09-05 15:00                         ` Kim F. Storm
2002-09-05 14:34                           ` Per Abrahamsen
2002-09-05 15:15                           ` Robert J. Chassell
2002-09-06  1:09                           ` Miles Bader
2002-09-05  2:46             ` Richard Stallman
2002-09-05 14:48               ` Robert J. Chassell
2002-09-06  1:05                 ` Miles Bader
2002-09-06 11:30                   ` Andreas Schwab
2002-09-06 11:57                   ` Modes: major, minor, context specific Robert J. Chassell
2002-09-06 20:03                   ` keymap in yank-excluded-properties Richard Stallman
2002-09-01 13:15     ` Richard Stallman

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=20020830.124308.81460907.Takaaki.Ota@am.sony.com \
    --to=takaaki.ota@am.sony.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).