Downloads:

2,681

Downloads of v 0.12.3.2:

2,129

Last Update:

6/26/2014

Package Maintainer(s):

Software Author(s):

  • elinks

Tags:

elinks web console browser http ftp text-only

ELinks - Full-Featured Text WWW Browser

0.12.3.2 | Updated: 6/26/2014

Downloads:

2,681

Downloads of v 0.12.3.2:

2,129

Maintainer(s):

Software Author(s):

  • elinks

ELinks - Full-Featured Text WWW Browser 0.12.3.2

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test


Validation Testing Unknown


Verification Testing Passed

Details

To install ELinks - Full-Featured Text WWW Browser, run the following command from the command line or from PowerShell:

>

To upgrade ELinks - Full-Featured Text WWW Browser, run the following command from the command line or from PowerShell:

>

To uninstall ELinks - Full-Featured Text WWW Browser, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade elinks -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade elinks -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure elinks installed
  win_chocolatey:
    name: elinks
    state: present
    version: 0.12.3.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'elinks' do
  action    :install
  version  '0.12.3.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: elinks,
    Version: 0.12.3.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller elinks
{
   Name     = 'elinks'
   Ensure   = 'Present'
   Version  = '0.12.3.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'elinks':
  provider => 'chocolatey',
  ensure   => '0.12.3.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install elinks version="0.12.3.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.

Description

ELinks is a program for browsing the web in text mode. The goal of the project has from the beginning been to provide a feature-rich text mode browser with an open patches/features inclusion policy and active development. One of these features is that ELinks includes Links-Lua which adds scripting capabilities to ELinks. ELinks was forked from the original Links browser written by Mikulas Patocka. It is in no way associated with Twibright Labs and their Links version. Please read to the history page for more information about the various Links versions and forks. Over the years many people have contributed to making ELinks what it is today.


In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
ELinks - Full-Featured Text WWW Browser 0.12.3.1 257 Thursday, June 26, 2014 Unknown
ELinks - Full-Featured Text WWW Browser 0.12.3 295 Thursday, June 26, 2014 Unknown

ELinks 0.12pre3
===============

   This is the third prerelease for ELinks 0.12.

   This release of ELinks is mostly licensed under version 2 of the GNU
   General Public License.  More permissive licences apply to some parts
   of it, and there is also one test file under the GNU Free Documentation
   License; please see COPYING for the list.

   User-visible changes since ELinks 0.12pre2
   ------------------------------------------

   Incompatibilities:

   * bug 1060: Regexp searching now requires the TRE library.
   * lzma disabled by default. It's rarely used and doesn't build with new xz.

   Fixed crashes:

   * critical: Fix double-free crash if EOF immediately follows /MAP>.

(Also fixed in ELinks 0.11.6.)

  • critical: Fix assertion failure if IMG/@usemap refers to a different
    file.
  • critical bug 1053: Fix crash if a download finishes after ELinks has
    closed the terminal from which the download was started. (Also fixed
    in ELinks 0.11.6.)
  • critical bug 1067: Fixed a crash in the RSS parser that ``configure
    --enable-html-highlight'' enables. (ELinks 0.12pre1 was the first
    release that supported RSS at all.)
  • Don't crash when the search-toggle-regex action is used and no regular
    expression support is compiled in.

Locales, charsets, and terminals:

  • major bug 1004: Ignore locales when comparing HTML element names and
    similar strings, so e.g. title'' matchesTITLE'' even in the
    Turkish locale. (Also fixed in ELinks 0.11.6.)
  • bug 153: Preserve Unicode characters in XBEL bookmark files.
    However, Unicode in URIs (really IRIs) does not work reliably yet;
    this is being tracked as bug 1066.
  • bug 885: Convert xterm titles to ISO-8859-1 by default, but add an
    option to disable this. When removing control characters from a
    title, note the charset. Don't truncate titles to the width of the
    terminal.
  • bug 1061: Correctly truncate UTF-8 titles in the tab bar.
  • minor: Clicking a link with the mouse activates that link, rather
    than the one selected with move-cursor-* actions. (Also fixed in
    ELinks 0.11.6.)
  • enhancement: Updated ISO 8859-7, ISO 8859-16, KOI8-R, and MacRoman.

Scripting:

  • Perl scripts can use modules that dynamically load C libraries, like
    XMLLibXMLSAX does.
  • bug 1069: ELinks didn't report ECMAScript errors, even if the
    ecmascript.error_reporting option was turned on. (This was a new
    bug in ELinks 0.12pre2.)

Everything else:

  • Preserve newlines in hidden input fields, and submit them as CRLF.
    Previously, they could turn into spaces or disappear entirely.
  • bug 1068: ELinks used to display a blank or truncated page if an
    HTTP/1.1 server sent a compressed body with incorrect Content-Length.
    That has now been fixed, and a new option (protocol.http.compression)
    has been added.
  • minor bug 761: When reading bookmarks from an XBEL file, distinguish
    attribute names from attribute values.
  • build bug 1047: Attempt to make inline functions satisfy C99 6.7.4p3
    so that ELinks can be built on OpenSolaris. (Also fixed in ELinks
    0.11.6.)

Kalle Olavi Niemitalo
Kamil Dudka
M. Vefa Bicakci
Miciah Dashiel Butler Masters
Peter Collingbourne
Petr Baudis
Witold Filipczyk

Known regressions

ELinks 0.12pre3 has the following bugs that were not in 0.11.6.
These should be fixed before the 0.12.0 release:

  • Bug 765 - Opening a new tab can ask about the document of the
    previous tab
  • Bug 943 - Crash: BFU points to a freed struct type_query

There is also one other bug scheduled for 0.12.0:

  • Bug 771 - Infinite loop is not well handled

These same bugs were listed in the 0.12pre2 announcement already. :-(


This package has no dependencies.

Discussion for the ELinks - Full-Featured Text WWW Browser Package

Ground Rules:

  • This discussion is only about ELinks - Full-Featured Text WWW Browser and the ELinks - Full-Featured Text WWW Browser package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or ELinks - Full-Featured Text WWW Browser, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus