From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@the-brannons.com
Subject: [Edbrowse-dev] edbrowse 3.6.2 is here
Date: Mon, 05 Dec 2016 16:44:12 -0800 [thread overview]
Message-ID: <87pol5lwdf.fsf@the-brannons.com> (raw)
I'll just quote from the CHANGES file:
3.6.2:
Read and convert utf16 and utf32 as per the byte order mark.
convert such files to utf8 or iso8859-1 as per the console setting,
though the latter is deprecated.
Convert back only if writing back out to the same file.
Enter high unicodes by the string ~u....;
where the dots are hex digits and the semi is optional.
New "list buffers" command (bfl) to get a list of buffers and filenames.
Read the attachment filename from the http content-disposition header and set the current filename accordingly.
The url could be replaced with foobar.zip, but that's what the web designer wanted.
If a file has a recognized suffix, with a stream plugin,
then typing g on a link within that file invokes the same plugin.
This is primarily used for .pls files, which are playlists,
and each URL therein is intended for a music player.
Other browsers seem to work this way.
Also there have been the usual bugfixes.
-- Chris
reply other threads:[~2016-12-06 0:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87pol5lwdf.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=edbrowse-dev@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).