ehmry
/
xdg_open_ng
1
0
Fork 1
Code Issues 1 Pull Requests Releases Activity
Replacement for xdg-open that uses Syndicate for messaging (Embrace, Extend, Extinguish).
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9 Commits
4 Branches
8 Tags
444 KiB
 
Branch: trunk
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'trunk'
${ noResults }
Emery Hemingway 9a301f487a
Start handlers at the Syndicate server 		3 days ago
src Start handlers at the Syndicate server 3 days ago
.gitignore Initial commit 2 months ago
README.md Make paths absolute and append file:// before publishing 2 weeks ago
exec.prs Start handlers at the Syndicate server 3 days ago
protocol.prs New protocol and configuration from Tony 2 months ago
uri_runner.pr Start handlers at the Syndicate server 3 days ago
xdg_open_ng.nimble Start handlers at the Syndicate server 3 days ago

README.md

xdg-open-ng

An xdg-open replacement that uses Syndicate and PCRE pattern matching to open URIs.

There are two utilites, xdg-open and uri_runner. The former connects to a shared Syndicate dataspace via a UNIX socket at $SYNDICATE_SOCK otherwise $XDG_RUNTIME_DIR/dataspace and as has no other configuration. The uri_runner component is intended to be managed by the Syndicate server thru which it receives configuration, see uri_runner.pr as an example.

The protocol.nim file is generated from the protocol.prs schema, a Tupfile file is provided to do this.

TODO

  • Fallback commands?