From: Carsten Dominik <carsten.dominik@gmail.com>
To: Phil Jackson <phil@shellarchive.co.uk>
Cc: emacs-orgmode@gnu.org, Michael Olson <mwolson@gnu.org>
Subject: Re: Re: patch: link to the log of an ERC session
Date: Wed, 16 Jan 2008 17:52:26 +0100 [thread overview]
Message-ID: <30FEEE51-7F9F-4CC6-A64B-F8B1814C3A9B@gmail.com> (raw)
In-Reply-To: <87sl143adg.fsf@shellarchive.co.uk>
On Jan 11, 2008, at 11:49 AM, Phil Jackson wrote:
> Michael Olson <mwolson@gnu.org> writes:
>
>>> I get a lot of my information from ERC/bitlbee so wrote this patch
>>> to
>>> allow for linking against the log associated with an ERC session.
>>
>> It's interesting that you're linking to the log file. I hadn't
>> thought of doing that before, but I like the idea. Planner's ERC
>> integration causes a new conversation to that person to be launched
>> when clicking on its generated link. I could see merits in each
>> approach.
>
> As I just make a 'file://' link to the log there is no reason org
> couldn't have an 'irc://' link too. Might be a little confusing for
> users having two places in the same buffer where C-c l could collect
> different links though :/
How about writing a little extension org-irc.el that extends the link
mechanism for both cases? I'd love to see more such extensions, and I
would be happy to distribute them with Org-mode, and to put them into
Emacs if the papers are in order.
In fact, I am thinking about putting more of the link stuff into
separate files, if I can find the time.
- Carsten
next prev parent reply other threads:[~2008-01-16 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 14:55 patch: link to the log of an ERC session Phil Jackson
2008-01-11 1:06 ` Michael Olson
2008-01-11 10:49 ` Phil Jackson
2008-01-16 16:52 ` Carsten Dominik [this message]
2008-01-16 19:06 ` Phil Jackson
2008-01-21 21:43 ` Phil Jackson
2008-01-22 13:19 ` Carsten Dominik
2008-01-27 18:53 ` Bastien
2008-01-28 17:43 ` Phil Jackson
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=30FEEE51-7F9F-4CC6-A64B-F8B1814C3A9B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mwolson@gnu.org \
--cc=phil@shellarchive.co.uk \
/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).