From: storm@cua.dk (Kim F. Storm)
Cc: Takaaki.Ota@am.sony.com, emacs-devel@gnu.org
Subject: Re: keymap in yank-excluded-properties
Date: 02 Sep 2002 17:02:31 +0200 [thread overview]
Message-ID: <5xelcc3054.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <E17lUYl-0006HZ-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> What's correct to do for yanking a table? Yanking the whole table
> ought to preserve its properties so that the table still functions as
> one. Yanking a part of the table which can act as a complete table in
> itself should also do that. However, yanking some of the text within
> the table, which is less than a whole table entry, should forget that
> it came from a table and treat it like any ordinary text.
>
> Does that make sense to you?
Yes, it makes a lot of sense to me.
The decision what to do must be taken when doing the yank (or
yank-rectangle), rather than the kill or copy, as there just too many
ways to get the (partial) table into the kill-ring, so the only place
where it makes sense to determine whether "the thing" is really a
table is when we yank it.
> If so, can you look for a design to
> achieve those results?
The design must provide for easily recognizing a table as a table.
It should not recognize something which might look like a table if
that wasn't actually part of a table before
It should recognize partial, but still valid tables, as tables.
I still think that my proposal for a yank-function text property (set
on the original table text, and used by yank and yank-rectangle to do
the yank) would do be a simple, yet powerful approach, as it would use
automatically copy that property to the kill-ring, so there is nothing
we need to add to basic functionality to achieve this.
I think the yank-function property should be removed from the inserted
text before yank calls that function; if necessary, that function is
responsible for adding the yank-function property again if that makes
sense.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-09-02 15:02 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
2002-09-01 13:14 ` Richard Stallman
2002-09-02 15:02 ` Kim F. Storm [this message]
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=5xelcc3054.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=Takaaki.Ota@am.sony.com \
--cc=emacs-devel@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).