From: Memnon Anon <email@example.com>
Subject: Re: Function: Extract link location to killring
Date: Sun, 3 Jul 2011 00:30:04 +0000 (UTC) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Bastien <email@example.com> writes:
> These two snippets could live on Worg -- can anyone add this to
> org-hacks.el (or any relevant place)?
Hope everythings okay, will check the html export when I wake up.
| commit d0d55a275fa2a78b864ed8eec48ed205aaae42f5
| Author: Memnon Anon <firstname.lastname@example.org>
| Date: Sun Jul 3 02:14:56 2011 +0200
| org-hacks.org: Reorganization, added "copy link dest to killring" hack
| * Remove "Enhancing the Org experience"
| Everything in org-hacks enhances the org experience.
| This headline conveys no information, even worse, it
| can easily end up a kitchen sink for all kinds of
| information that eventually no one will find anymore.
| Distributed hacks to new headlines:
| * New Headlines
| - Structure Movement and Editing
| - Org Table
| - Capture and Remember
| - Handling Links
| * Remove Speed Commands
| Speed commands are no hack but a regular feature for quite
| a while now. So far, there was only a link to the manual
| and "add your stuff here". Definately worth a headline
| when there is actually content to put in there.
next prev parent reply other threads:[~2011-07-03 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 9:31 Copy link at point Christian Moe
2011-06-23 11:03 ` Christian Moe
2011-06-23 12:00 ` Memnon Anon
2011-06-23 12:56 ` Eric S Fraga
2011-06-23 15:42 ` Christian Moe
2011-06-23 12:17 ` Function: Extract link location to killring (was: Copy link at point) Memnon Anon
2011-06-23 14:20 ` Function: Extract link location to killring Christian Moe
2011-07-02 9:29 ` Bastien
2011-07-03 0:30 ` Memnon Anon [this message]
2011-07-03 11:27 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).