all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexandros Prekates <aprekates@posteo.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Killing org hyperlinks with one key
Date: Fri, 10 Jun 2022 09:45:27 +0000	[thread overview]
Message-ID: <20220610124527.64c85ad7@enoush2o> (raw)
In-Reply-To: <87pmjixkut.fsf@dataswamp.org>

On Thu, 09 Jun 2022 11:11:06 +0200
Emanuel Berg <incal@dataswamp.org> wrote:

> Alexandros Prekates wrote:
> 
> >>> Trying to kill an org link+description  
> >> 
> >> You have an example what that looks like/is?  
> > 
> > That's how it look complete: [[LINK][DESCRIPTION]]
> >
> > And Org by default displays only the Description part.
> > So i'd like a function to kill the complete hyperlink while
> > it's not visible completely.  
> 
> Yes, but how does it look in its original context?

In the original context , if i understand you, it looks
as simple text with a different face and underlined.

> 
> One can't write a function without it ...
> 
> But you can do it yourself ... use `kill-new' and
> `thing-at-point',
> 
>   (kill-new (thing-at-point 'url t))
> 
> Lousy that Org cannot do this already!
> 

Thanks for the idea of using thing-at-point.

I'm also checking Invisible Text .

Here is the fuction that toggleis org links display:
(defun org-toggle-link-display ()
  "Toggle the literal or descriptive display of links."
  (interactive)
  (if org-link-descriptive (remove-from-invisibility-spec '(org-link))
    (add-to-invisibility-spec '(org-link)))
  (org-restart-font-lock)
  (setq org-link-descriptive (not org-link-descriptive)))

buffer-invisibility-spec seems to hold invisible text.


Alexandros.





  reply	other threads:[~2022-06-10  9:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  7:34 Killing org hyperlinks with one key Alexandros Prekates
2022-06-09  7:41 ` Emanuel Berg
2022-06-09  8:41   ` Alexandros Prekates
2022-06-09  9:11     ` Emanuel Berg
2022-06-10  9:45       ` Alexandros Prekates [this message]
2022-06-10 18:36         ` Emanuel Berg

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

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

  git send-email \
    --in-reply-to=20220610124527.64c85ad7@enoush2o \
    --to=aprekates@posteo.net \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.