开源软件名称：

开源软件地址：

开源编程语言：

开源软件介绍：

Build status:

Grasp is a browser extension for Chrome and Firefox, which adds a button/keybinding to capture current page title and url, possibly selected text, additional comments or tags and adds it into your Org Mode file.

Screenshot, short demo.

• Chrome
• Firefox
• or, install from a zip: releases.

Running

In the simplest setup, the server runs locally, and you can use 'localhost' version of the extension. If you have to work on a computer where you can't run python scripts, or your target capture file is just not there, you can selfhost the server part elsewhere and use the 'any host' version. Don't forget to set the endpoint in extension settings!

1. Install server counterpart as systemd service (to autostart it): server/setup --path /path/to/your/capture.org [--port <custom port>] [--template <custom org-capture template>].

   Or alternatively, just run it directly if you don't want to autostart it: server/grasp_server.py --path /path/to/your/capture.org [--port <custom_port>] [--template <custom org-capture template>].

2. Install chrome extension and configure hotkeys

That's it! If you're using custom port make sure it's the same as in the extension settings (default is 12212).

Configuration

Here you can find some references for the --template syntax.

If you are looking for more flexible formatting that's not supported by template syntax, see config.py.example. You can modify it to your liking and pass as --config to grasp_server/setup scripts.

Motivation

Why use org-capture? Well, it's hard to explain, maybe some other time... However, if you do know you want to use it instead of/alongside your browser bookmarks, by default you don't have much choice and have to copy everything manually. For an experienced enough org-mode user it's no less than a torture.

This tool:

• + shows a notification when capturing fails/succeeds, so you won't lose your notes

• + doesn't require always running Emacs, simply appends an org-mode text entry to a file

• + can capture things that org-protocol can't handle (e.g. extra comment or tags)

• + can potentially use any plaintext format as a storage.

  E.g. you might be more of a Markdown or Todo.txt fan (let me know if you are interested in that!).

• - doesn't talk to Emacs, so can't benefit from Emacs capture templates

  E.g. currently you can't point at a specific header in an org file, it would just append at the end.

• - requires running a small HTTP server

  However, there are no dependencies apart from python3, so in many ways, it's even more portable than Emacs.

Comparison with similar tools:

org-capture-extension

• - relies on org-protocol and MIME handler: flaky for many people and has no feedback whether capture failed or succeeded

  Losing few days of captured stuff due to MIME handler mysteriously not working was the main motivator for me to develop grasp.

• - requires always running Emacs, which might not be the case for some people

• + relies on org-protocol, so can potentially be better integrated with Emacs and your org-mode files

org-protocol-capture-html

Same pros/cons as org-capture-extension as it's relying on org-protocol.

In addition:

• + using a bookmarklet, hence browser-agnostic
• + capable of on the fly HTML to org-mode markup conversion

Requirements

No third party dependencies! Just python3.

Potential improvements

• see todos

Permissions used

• http://localhost/capture for talking with the backend

  If you want to use an external URL as an endpoint, you will be prompted for a permission dynamically.

• storage for settings

• notifications for showing notification

• activeTab for requesting page info

Building & developing

The most up-to-date instructions should be in CI config.

You need npm for building the extension.

npm install
./build --target <browser> # e.g. ./build --target chrome or ./build --target firefox

After that you can find the extension in dist directory and 'Load unpacked** if necessary. There is also Flow and Eslint set up.

testing and linting

Check CI config to figure out all the checks I'm doing.

The only test(s) that don't run on CI at the moment (e.g. due to lack of X server) are marked with @skip_if_ci. You can run them manually though.

Extra tests (not integrated in CI yet):

• scripts/test_with_browser.py

publishing

• run ./publish to generate extension zip files

• firefox: ./build --firefox --release --lint --sign

  After than, upload the signed xpi file on AMO

• chrome: ./build --chrome --release --lint

  After that, upload the zip (generated by publish script) on Web store

Credits

• Icon made by Freepik from www.flaticon.com, licensed by CC 3.0 BY
• Original Org Capture extension
• Boilerplate for Webpack Chrome extension