emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: emacs-orgmode@gnu.org
Subject: marking out-links
Date: Sat, 05 Jul 2008 13:00:40 +0200	[thread overview]
Message-ID: <871w288ujr.fsf@mithrandir.homeunix.net> (raw)


Hi,

One featurette that i would find useful is the possibility of
distinguising link types visually: for instance, having the link text
overlay display an additional mark (say, a * or a fancy unicode arrow)
when it is an http[s] or ftp link (as opposed to a link to a local file,
email, etc.). If providing the basic functionality is not difficult, one
can think of additional customizability like associating different
markers to different protocols and so on.

On a related note, it would also be useful to have a mode or command to
see the URL of the current link echo-ed in the minibuffer. I currently
use a quick-and-dirty command for that (it also puts the link in the
kill ring for convenience):

(defun jao-org-copy-link-at-point ()
  (interactive)
  (if (thing-at-point-looking-at "\\[\\[\\([^]]+\\)\\]\\[[^]]+\\]\\]")
      (let ((link (substring-no-properties (match-string 1))))
        (kill-new link)
        (message "%s" link))
      (message "No link at point")))
(define-key org-mode-map "\C-cv" 'jao-org-copy-link-at-point)

but this doesn't work as an 'show link in the mini-buffer, in the sense
that i have to press C-cv to see the link.

What do you think?

Cheers,
jao
-- 
In this age, the mere example of nonconformity, the mere refusal to bend
the knee to custom, is itself a service.
 -John Stuart Mill, philosopher and economist (1806-1873)

             reply	other threads:[~2008-07-05 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05 11:00 Jose A. Ortega Ruiz [this message]
2008-07-07 15:56 ` marking out-links Carsten Dominik
2008-07-07 17:38   ` Jose A. Ortega Ruiz

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.orgmode.org/

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

  git send-email \
    --in-reply-to=871w288ujr.fsf@mithrandir.homeunix.net \
    --to=jao@gnu.org \
    --cc=emacs-orgmode@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/org-mode.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).