unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] Make eshell ‘ls’ output clickable.
Date: Fri, 07 Jul 2017 21:54:11 -0400	[thread overview]
Message-ID: <87wp7jith8.fsf@lifelogs.com> (raw)
In-Reply-To: CAP_d_8VxB9xZVkbX+66ouefrEvZ-99RtXCPQ176bMhw_QhwieA@mail.gmail.com

On Fri, 7 Jul 2017 23:30:23 +0700 Yuri Khan <yuri.v.khan@gmail.com> wrote: 

YK> On Fri, Jul 7, 2017 at 11:10 PM, Ted Zlatanov <tzz@lifelogs.com> wrote:
>> I feel this indicates a wider need, not specific to eshell, to dig out
>> "things" from text and act on them, guessing their proper handler.
>> Maybe it already exists?

YK> ‘find-file-at-point’ comes to mind. Maybe it could be extended, or
YK> made one of backends, to ‘dwim-at-point’.

That would be cool. I think Drew's post was along those lines too, but
crucially I'm suggesting that the *source* of the text (in this case,
eshell) should tag the text region with some property like "this came
from ls so it's probably file names, permissions, dates..."

That doesn't exist, does it? If I were to implement a first rough cut,
what should the property look like? Maybe a list of symbols?

There was a recent question on Reddit[1] about tagging lines as you
browse text and then deleting them all later. This could be another use
for this kind of ad-hoc text property, but in this case the property
would be created by the user instead of by the originator of the text.

Ted

[1] https://www.reddit.com/r/emacs/comments/6jfctn/mark_lines_in_buffer_for_mass_delete/




  parent reply	other threads:[~2017-07-08  1:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06  4:31 [PATCH] Make eshell ‘ls’ output clickable Matthew Bauer
2017-07-07 15:08 ` Nicolas Petton
2017-07-07 16:10   ` Ted Zlatanov
2017-07-07 16:30     ` Yuri Khan
2017-07-07 18:25       ` Drew Adams
2017-07-08  1:54       ` Ted Zlatanov [this message]
2017-07-07 15:15 ` Nicolas Petton
2017-07-07 15:47   ` Eli Zaretskii

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=87wp7jith8.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).