Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: magnus@therning.org (Magnus Therning)
Subject: [sup-talk] Tilde in maildir/mbox paths
Date: Fri, 07 Sep 2007 19:47:59 +0100	[thread overview]
Message-ID: <1189190787-sup-1919@tatooine> (raw)
In-Reply-To: <20070907092109.GB23285@die.therning.org>

Excerpts from Magnus Therning's message of Fri Sep 07 10:21:09 +0100 2007:
> On Fri, Sep 07, 2007 at 08:37:21 +0100, Magnus Therning wrote:
> >I find it useful to be able to stick '~' in paths so here's an attempt
> >at a patch that allows a source with the URI maildir:~/mail/in.
> >
> >Two comments:
> >
> > 1. I didn't really know where to stick expand_uri so it's duplicated in
> >    Maildir and Mbox.  This is far from ideal.  Please tell me where it
> >    belongs.
> 
> An obvious place would of course be the parent class Source.  For some
> strange reason that didn't enter my mind while I was hacking on this.

A modified patch is attached.

-- 
Magnus Therning                             (OpenPGP: 0xAB4DFBA4)
magnus?therning?org             Jabber: magnus?therning?gmail?com
http://therning.org/magnus

What if I don't want to obey the laws? Do they throw me in jail with
the other bad monads?
     -- Daveman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup_514-2.diff
Type: application/octet-stream
Size: 2273 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070907/4d16512d/attachment.obj 


  parent reply	other threads:[~2007-09-07 18:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  7:37 Magnus Therning
     [not found] ` <20070907092109.GB23285@die.therning.org>
2007-09-07 18:47   ` Magnus Therning [this message]
2007-09-14  2:45 ` William Morgan
2007-09-14 21:38   ` Magnus Therning
2007-09-14 22:44     ` Magnus Therning
2007-09-15  3:41       ` William Morgan
2007-09-15 10:19         ` Magnus Therning
2007-09-17 17:30           ` William Morgan

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=1189190787-sup-1919@tatooine \
    --to=magnus@therning.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox