On Sunday, 30 July 2000 at 00:32, David T-G wrote:
> Hi, folks --
>
> When running 0.95.4i and attaching a file, mutt defaulted to searching my
> current directory. Under 1.2.4i mutt now apparently defaults to my
> $folder even for ordinary file attachments. Although surprising, that's
> not so bad, because I can simply start my filename with ./ and then let
> mutt do the completion.
>
> When I both navigate out of $folder *and* start with ./ and let mutt do
> filename completion, though, the path to the attached file is my full
> path with a ~ contraction -- like specifying
>
> ./filenamepart<tab>
> [select from list]
>
> gives me an attachment labeled
>
> ~/some/subdir/path/filenamecomplete
>
> It seems that the only way to get just the filename is to type they whole
> thing out, either with a leading ./ or (since it's now useless) without.
>
> The end goal is to not provide any local filesystem clues when sending out
> attachments, but I'd sure like to use mutt's navigation and completion.
> What can I do?
Hmmm. I believe when the attachment actually gets sent out only the
basename will be used. So even if you send
/home/davidtg/secret/illicit/company/secrets/mangochicken.recipe
all that will appear in the content description will be
mangochicken.recipe
But personally I'm not thrilled with starting out in $folder. Since I
use IMAP, my $folder almost never points to where I keep the things I
want to attach...
PGP signature
