-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Add capture-context extension #16212
Conversation
- gitignore - merge conflicts from raycast github nameclash - Pull contributions - gitignore - fix lints and publish errors - capture with clipboard contents (command) - url and markdown capture Orion - preference defaults - manage directory command - fix path issue - preferences - delete - clean up - simplify commands, remove two - delete capture-with-comment command - CaptureData struct update - add comment to screenshots in directory - comment-view of latest captures - quick capture - add frontmostapp to meta - initial setup
Congratulations on your new Raycast extension! 🚀 You can expect an initial review within five business days. Once the PR is approved and merged, the extension will be available on our Store. |
- readme - remove legacy code - readme + examples - readme
- raycast warnings - update readme links - applescript url sanitize - improved capture speed performance - mailto bug - cut most of comment form - halfed the code 🙃 - comments do not overwrite json - favicon display list - simpler - comment capture ui - add title and favicon to captureData - screenshot loading in parallel - screenshots to capture - screenshot comment moves screenshot - flatten schema, remove legacy code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused about the purpose and who would benefit for an extension like this - can you please help me figure that out
Hey sorry I should've read the guidelines better.
I wanted to have a few of my friends use my extension through the store but
I guess it's easier to send them the GH repo.
The extension is basically a cross-app clipper. It takes the context-info
(browsertab, selectedText, app and so on) and saves it to a specified
directory.
I mostly use it to bookmark pages and have a raw log that AI can analyze.
It's ok if you disregard me trying to publish it - it's mostly for my own
workflow
Cheers,
…On Wed, Jan 15, 2025 at 1:13 PM Per Nielsen Tikær ***@***.***> wrote:
***@***.**** requested changes on this pull request.
I'm a bit confused about the purpose and who would benefit for an
extension like this - can you please help me figure that out
—
Reply to this email directly, view it on GitHub
<#16212 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3J2AV4MUIFOK6BDTW5BST2KZGFVAVCNFSM6AAAAABUYS7TTGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKNJSGQ2DQMRZGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You could create an organization and get your friends to join that; that way, you can share it as a private extension in the private organization store - that way they'll also get updates 😊 |
Ah great thanks that's a good idea
…On Wed, Jan 15, 2025 at 2:25 PM Per Nielsen Tikær ***@***.***> wrote:
You could create an organization and get your friends to join that; that
way, you can share it as a private extension in the private organization
store - that way they'll also get updates 😊
—
Reply to this email directly, view it on GitHub
<#16212 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3J2AVZ55KDVG65QDOLU632KZOUJAVCNFSM6AAAAABUYS7TTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJSHA2TEMRQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Description
Screencast
Checklist
npm run build
and tested this distribution build in Raycastassets
folder are used by the extension itselfREADME
are placed outside of themetadata
folder