-
Notifications
You must be signed in to change notification settings - Fork 20
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
workflow query #31
Comments
No particular reason but:
I might consider the C-c C-c approach, though. It might take m e a while; a PR is welcome. |
btw, my annots are conscious! :) just often i want to restore original context. i'm not annotating other people's work, but my own. |
Same re annotations for my own notes :) I just don’t use C-c C-c very often. I’ll see what I can do. |
@mooseyboots you might find my configuration below useful. It's catered to ebook reading, but the commented portion is applicable to all (defun my-reading-make-highlight-annotation ()
"Highlight text and activate the annotation notes for input.
This single function can be called for both EPUBs and PDFs."
(interactive)
(cond ((eq major-mode 'nov-mode)
(apply 'org-remark-mark (org-remark-region-or-word)) ;; mark active region
(org-remark-view (- (point) 1)) ;; view newly created marginal notes
(switch-to-buffer "*marginal notes*") ;; switch to marginal notes buffer
(evil-org-open-below 1))
((eq major-mode 'pdf-view-mode)
(pdf-annot-add-highlight-markup-annotation pdf-view-active-region)
(evil-insert 1)
))) You could bind |
This is a good suggestion. I will try to add some snippet like this in the user manual/README. |
hi again,
i have a query about workflow.
to me it would make sense if a) when you create a remark the notes buffer also opens and is active, and b) you cd hit
C-c C-c
or similar when done to save and close the notes buffer and return to your work.i guess this is based on a lot of other workflow habits, like annotating pdfs, or org-capture, etc.
it's also fast, especially when all you need to do is attach something to your text, and move on right away.
is there a reason
org-remark
avoids this approach? or am i doing it wrong maybe?The text was updated successfully, but these errors were encountered: