ndmitchell / ndmitchell/hoogle

--local does the opposite of what it says on the tin

Open
#286 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
803
Forks
152
PR merge metrics
No merged PRs in 30d

Description

The documentation says:
"Allow following file:// links, restricts to 127.0.0.1", but in fact when I turn on --local, then I'm able to access browse on a remote machine because the links hoogle generates are not preceded with file://
This is very confusing.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the --local option and the code that generates browse links, then compare its behavior with the documented file:// restriction and 127.0.0.1 access. Confirm how links behave for local and remote machines, and consider the issue done when the implementation and documentation agree about --local.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.