zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: MIME functions
Date: Wed, 10 Sep 2003 10:37:40 +0100	[thread overview]
Message-ID: <13790.1063186660@csr.com> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Wed, 10 Sep 2003 10:58:00 +0200." <2623.1063184280@gmcs3.local>

Oliver Kiddle wrote:
> > +Repeated calls to tt(zsh-mime-setup) do not override the existing
> > +mapping between suffixes and executable files unless option tt(-r) is
> > +given.  Note, however, that this does not override existing suffix
> 
> Would -f perhaps be more conventional than -r (for force, as used by
> cp, ln etc).

You're right; the reason for -r was originally I was just going to make
it reset, but I decided there was no point unless it reinitialized, so
-f would make more sense.

> The /etc/mailcap has a lot of crap in it here so it might be nice if
> there was an option to specify that the system mailcap should not be
> used or to specify an alternate list of mailcap files. Perhaps using
> zstyle instead of an option. Could be quite a lot of scope for using
> zstyle to override mailcap entires and other configuration.

Yes, and I think there are plenty of places where utilities stick their
own mailcap files which might or might not be useful.  A style for
the sets for mailcap and mime.types files (maybe the style should be
mime-types for consistency) and possibly browsers would be useful as
well as very easy.  I'll make the styles begin with :mime: unless anyone
has a better idea.

> If you want to add konqueror to this, note that the equivalant to
> -remote would be to use something like:
> 
> dcop $(dcop|grep konqueror) konqueror default openBrowserWindow $url

Yuk.  I'll try this at home.

> And, I hate to whinge but can we not be consistent on coding
> style/indentation across scripts in zsh. Completion functions written
> by Sven or me all use two spaces.

Most of my recent functions seem to use two spaces, too.

I will probably commit the files after another set of changes without
posting them again when I get a chance to fiddle.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  reply	other threads:[~2003-09-10  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 20:02 Peter Stephenson
2003-09-10  8:58 ` Oliver Kiddle
2003-09-10  9:37   ` Peter Stephenson [this message]
2003-09-14 19:46     ` Peter Stephenson

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=13790.1063186660@csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).