Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README changes for Microsoft Edge #24

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Alfred Chrome History Workflow
# Alfred Chrome/Microft Edge History Workflow

Access your Google Chrome history from Alfred with `ch {query}`.

Expand All @@ -20,7 +20,7 @@ Then run `make dev` to install requirements and set the repository up to be used

The workflow should work out of the box with the `ch` prefix. If you'd like to change this, update the keyword in the Alfred workflow's script filter.

### Choosing the correct Google Chrome profile directory
### Choosing the correct Google Chrome / Microsoft Edge profile directory

The Alfred script filter is set up to use the default Chrome profile located in `~/Library/Application Support/Google/Chrome/Default`. If you need to use a different profile, update the `PROFILE` environment variable in the Alfred workflow's script filter. This could be the necessary if you have signed in to Chrome with different or multiple accounts, and usually the profile directory is located in something like `Profile 1`. If that is the case, the entire Script contents in the workflow's script filter would be:

Expand All @@ -30,6 +30,8 @@ PATH="env/bin:$PATH"
python chrome.py "${PROFILE}" "{query}"
```

> For Micrsoft Edge you can use ~/Library/Application Support/Microsoft Edge/Default

In a terminal, the following command can help you find the exact location of the profile directory that the workflow needs:

```sh
Expand Down