edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  mailx, plugin commands, mime, new sourcefile
Date: Mon, 13 Apr 2015 16:33:57 -0400	[thread overview]
Message-ID: <20150313163357.eklhad@comcast.net> (raw)
In-Reply-To: <20150413201636.GI9150@toaster.adamthompson.me.uk>

> but I'd like it if the type attribute was optional

I was looking at this stuff and asked myself, "what the hell is type for?"
It is used nowhere, except one place, where the string
is copied into a mime object in the js world.
There is such an object for each mime entity in the config file.
That object wants a type attribute, I don't know what for.
We could probably do without it just fine,
or maybe just copy the description in there.

> I'd also probably rename this as plugin since it's now more than just mime type handlers.

I think that's a great idea, will probably do that
unless someone objects.
Not sure if I will retroactively change all the variables in the source code,
but at least the config file syntax.

> Should this be plugin.c rather than mime.c?

Yes I think so, I'll do a git rename soon.
That's easy. Thanks.


Karl Dahlke

  reply	other threads:[~2015-04-13 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 16:00 [Edbrowse-dev] mailx Karl Dahlke
2015-04-12 19:36 ` Adam Thompson
2015-04-12 20:46   ` [Edbrowse-dev] mailx, plugin commands, mime, new sourcefile Karl Dahlke
2015-04-13 20:16     ` Adam Thompson
2015-04-13 20:33       ` Karl Dahlke [this message]
2015-04-14  6:49         ` Adam Thompson

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=20150313163357.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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;
as well as URLs for NNTP newsgroup(s).