Re: [O] ?dynamic-line-length?
On Friday, 9 May 2014 at 17:16, Nick Dokos wrote: Sharon Kimble boudic...@skimble.plus.com writes: How can I have dynamic-line-lengths, or in other words, the line in an org-mode document is 78, but when two frames are opened side-by-side, one on the left and one on the right, our original documents line length now adapts itself to fit the decreased window size, and yet all of the line and document can very easily be read and written without having to move the buffer left or right. Can it be done please? If so, how? Try the options in the Options-Line wrapping in this buffer menu. Sharon, this option turns on visual-line-mode and works very well especially in conjunction with org-indent-mode, by the way. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-923-g233c11
Re: [O] Export all headlines when some are set with :export:
On 2014-05-10 05:11 John Hendy wrote: In creating a packing/buy list for an upcoming camping trip, I wanted two exports: - one for things to buy - one for everything on the list for packing If these two lists are disjoint you could put each of them under its own subtree and export these subtrees seperately. Just press C-s in the export dispatcher. HTH, -- Alexander Baier
Re: [O] [ANN] Gnorb: Glue code between Gnus, Org, and BBDB
Alan Schmitt alan.schm...@polytechnique.org writes:
I usually avoid putting links in my tasks. For instance, the task
I generated from your email to the list looks like this:
TODO Reply to this when I will have tried gnorb
:@fun:
[2014-05-07 Wed 11:25]
[[gnus:lists.orgmode#87r446bcut@ericabrahamsen.net][Email from Eric
Abrahamsen: {O} {ANN} Gnorb: Glue code bet (Wed, 07 May 2014 09:23:54 +0800)]]
Would it be difficult to handle such emails when the link is inside the
TODO, instead of in the heading?
Not at all! In fact, the next tweak for this is an option allowing you
to expand the scope of the scan for links. I'll probably default it to
checking the first paragraph of the entry text, but you'll be able to go
all the way to 'subtree.
I can of course change my capture format. I'm just wondering why you
prefer to have the link in the mail.
Heck no I don't want you to change your format! I'm very sensitive to
issues of mental overhead and workflow/file-format lock-in with this
package. The whole point is to help you think *less*, not more, and I
don't want people having to write a bunch of code or change their files
to make it work. Ideally everything would just happen by calling
functions, and it will be the responsibility of those functions to
look at your TODO structure and do the right thing.
Actually, let me hijack this for a second and ask a more general
question. I announced the package at this stage, and not when it was
more complete, because the next thing to do is flesh out its email
handling capabilities, and I'd love to get feedback on that first.
I'm writing two more functions to complement `gnorb-org-handle-mail'. In
the end there will be three:
1. A function that says make an Org todo out of the email I'm sending
now (to keep track of conversations that need following-up).
2. A function that says this email I just received is relevant to some
Org heading, and should trigger a TODO state-change or a note on that
heading. It will be able to suggest the correct heading.
3. A function that says send an email by reading the current Org
heading and doing what I what. That's `gnorb-org-handle-mail'.
Everything else just depends on how you've set up your capture
templates, and how you like to structure your mail-related TODOs. I
don't want to enforce anything else, but I want those three functions to
be good at guessing how you do things, and I'll provide user options to
help them guess correctly. In particular, how `gnorb-org-handle-mail'
interprets the heading under point is important.
I just said I don't want to enforce anything, but one thing I want to
strongly *encourage* is the use of the LOGBOOK drawer to keep track of
email threads/conversations. By using `org-log-into-drawer', the @
cookie for TODO keywords, and `org-add-note', you can keep track of all
the important developments in an email conversation, using links to
specific messages. I do a fair amount of business negotiation via email,
and this is pretty crucial for me. I end up with headings looking like
this:
* WAIT Sort out copyright agreement with [[bbdb:johnbob]]
:LOGBOOK:
- State WAIT from REPLY [2014-05-08 Sat 09:45] \\
I told him that might work, but we'd need to limit the language zone
- State REPLY from WAIT [2014-05-07 Sat 15:09] \\
He [[gnus:link][wrote back]] and proposed 14% royalties
- Note taken on [2014-05-06 Sat 12:56] \\
Mattbob [[gnus:link][wrote]] and reminded me to ask about digital rights
- State WAIT from EMAIL [2014-05-04 Fri 13:25] \\
Wrote to Johnbob and proposed terms.
:END:
:PROPERTIES
:GNORB_MSG_IDS: 46bcut@ericabrahamsen.net jj8m@johnbob.fr
:END:
I'd like gnorb to do all the complicated bits for you. You should just
be able to call whichever of the three functions is relevant, and then
gnorb will put you in the right place, with a link loaded, to take a
note or annotate a state-change. In the above example,
`gnorb-org-handle-mail' should see that there are gnus links in the
LOGBOOK, and start a reply to the most recent one.
If you only ever use email TODOs as a one-off send-or-reply reminder,
then everything is much simpler, of course.
So that's what I'm thinking. The code is half-done. If anyone has
any requests or objections or demands, let's have them!
Regarding your daily flow, it seems that bbdb is very central to how you
work. Do you simply use it as a backend linked to the agenda view, or do
you often navigate your bbdb records? If you ever have the time to write
or do a screencast of your work flow, I would be most interested in
learning more about it.
That would be a very dull screencast :)
I use the BBDB a lot because when I think now I have to do XYZ, that
often starts with thinking of the people involved with the task. So I go
to the record in BBDB, and then call `gnorb-bbdb-mail-search' to see
messages from them, or `gnorb-bbdb-tag-agenda'
Re: [O] Set tags in region
Hello John, On 2014-05-10 04:53 John Hendy wrote: Just curious of there's a way to set the tags in a region all at once? You could also takle this with keyboard macros, see (info (Emacs) Keyboard Macros). [Evaluate that expression in emacs to see the relevant manual entry.] Define a macro that tags one specific headline and then execute it on the current region with `C-x C-k r'. HTH, -- Alexander Baier
[O] Org-hide face leaking out to org-columns view
Hi! It seems that if you use #+STARTUP: indent the org-hide face used for the hidden stars will remain when using the org-columns view, resulting on, in my case, white on gray. Is there a workaround to this that I’m not thinking of?
Re: [O] [ANN] Gnorb: Glue code between Gnus, Org, and BBDB
On 2014-05-10 12:32, Eric Abrahamsen e...@ericabrahamsen.net writes:
Alan Schmitt alan.schm...@polytechnique.org writes:
I usually avoid putting links in my tasks. For instance, the task
I generated from your email to the list looks like this:
TODO Reply to this when I will have tried gnorb
:@fun:
[2014-05-07 Wed 11:25]
[[gnus:lists.orgmode#87r446bcut@ericabrahamsen.net][Email from Eric
Abrahamsen: {O} {ANN} Gnorb: Glue code bet (Wed, 07 May 2014 09:23:54
+0800)]]
Would it be difficult to handle such emails when the link is inside the
TODO, instead of in the heading?
Not at all! In fact, the next tweak for this is an option allowing you
to expand the scope of the scan for links. I'll probably default it to
checking the first paragraph of the entry text, but you'll be able to go
all the way to 'subtree.
That would be great indeed.
I can of course change my capture format. I'm just wondering why you
prefer to have the link in the mail.
Heck no I don't want you to change your format! I'm very sensitive to
issues of mental overhead and workflow/file-format lock-in with this
package. The whole point is to help you think *less*, not more, and I
don't want people having to write a bunch of code or change their files
to make it work. Ideally everything would just happen by calling
functions, and it will be the responsibility of those functions to
look at your TODO structure and do the right thing.
A more robust alternative than looking at the note's text could be to
have a property with the link to the mail. (Later) I see that your
LOGBOOK example uses a property to track the message. Could this be
considered as the link? And I also see you only record the message
id. How do you get to the right folder using it?
Actually, let me hijack this for a second and ask a more general
question. I announced the package at this stage, and not when it was
more complete, because the next thing to do is flesh out its email
handling capabilities, and I'd love to get feedback on that first.
For comparison, my email handling workflow is very simple. I have
a capture with link template that looks like this, that I can use
from inside gnus:
#+begin_src emacs-lisp
(T todo with link entry (file refile-orgx.org)
* TODO %?\n %U\n\n%a)
#+end_src
I'm also making sure the link text has enough information to find the
mail again if it's moved (I would love a more robust linking system,
maybe based on notmuch, but this works well enough for the moment). To
do so, I set `org-email-link-description-format' to Email %c: %.30s (%d).
To follow a link, I don't simply click on it as it usually breaks my
carefully crafted layout for my agenda and todo files. So I have a very
simple function that creates a frame to display the link:
#+begin_src emacs-lisp
(defun as/copy-link-and-open-in-new-frame ()
(interactive)
Copies the next link found and opens it in a new frame
(org-next-link)
(let ((link (org-element-property :raw-link (org-element-link-parser
(make-frame '((name . follow-link)))
(select-frame-by-name follow-link)
(org-open-link-from-string link)))
#+end_src
This setup is why I'm so interested in gnorb: it's too much manual
manipulation and friction.
I'm writing two more functions to complement `gnorb-org-handle-mail'. In
the end there will be three:
1. A function that says make an Org todo out of the email I'm sending
now (to keep track of conversations that need following-up).
2. A function that says this email I just received is relevant to some
Org heading, and should trigger a TODO state-change or a note on that
heading. It will be able to suggest the correct heading.
3. A function that says send an email by reading the current Org
heading and doing what I what. That's `gnorb-org-handle-mail'.
These three functions would be most useful indeed.
I just said I don't want to enforce anything, but one thing I want to
strongly *encourage* is the use of the LOGBOOK drawer to keep track of
email threads/conversations. By using `org-log-into-drawer', the @
cookie for TODO keywords, and `org-add-note', you can keep track of all
the important developments in an email conversation, using links to
specific messages. I do a fair amount of business negotiation via email,
and this is pretty crucial for me. I end up with headings looking like
this:
* WAIT Sort out copyright agreement with [[bbdb:johnbob]]
:LOGBOOK:
- State WAIT from REPLY [2014-05-08 Sat 09:45] \\
I told him that might work, but we'd need to limit the language zone
- State REPLY from WAIT [2014-05-07 Sat 15:09] \\
He [[gnus:link][wrote back]] and proposed 14% royalties
- Note taken on [2014-05-06 Sat 12:56] \\
Mattbob [[gnus:link][wrote]] and reminded me to ask about digital rights
- State WAIT from EMAIL [2014-05-04 Fri 13:25] \\
Wrote to Johnbob
[O] wish: provide flush_right/right_aligned text rendering directive
Dear org-mode developers, org-modes default for typographic alignment is flush left (or left aligned) (at least for (ltr scripts). There is a #+BEGIN_CENTER formatting directive, though. I wish for a #+BEGIN_FLUSH_RIGHT (#+BEGIN_RIGHT_ALIGNED) directive in order to render text right flushed (right aligned) in export backends. [For the sake of consitenzy one might also wish for a #+BEGIN_JUSTIFIED directive, but at the moment I have no use case for this.] Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.-
Re: [O] Export all headlines when some are set with :export:
On May 9, 2014 11:32 PM, Nick Dokos ndo...@gmail.com wrote: John Hendy jw.he...@gmail.com writes: In creating a packing/buy list for an upcoming camping trip, I wanted two exports: - one for things to buy - one for everything on the list for packing My strategy was to tag things to buy with :export: (perhaps foolish, but it was the obvious choice to selectively export them) to create my shopping list. I'd also like an alternate export with all headlines in the subtree exported. Now the list is done like that, but I'm not sure how to export everything without undoing all the tags on the buy list items. I'm thinking I should have done something like a :buy: tag, then set SELECT_TAGS to target those items, followed by removing that export option and exporting as normal to get them all. Just thought I'd see if there was a way to override the function of :export: as it typically behaves. An empty SELECT_TAGS selects everything I believe: --8---cut here---start-8--- #+SELECT_TAGS: * a :export: * b * c * d :export: --8---cut here---end---8--- Then you can comment it out to get just the :export:ed headlines. But a semantically meaningful tag seems better to me. Awesome, and I'll keep that in mind. Agreed re. the better strategy with non-org tags, which is what I ended up doing. Thanks! John -- Nick
Re: [O] Set tags in region
On May 9, 2014 11:21 PM, Nick Dokos ndo...@gmail.com wrote: John Hendy jw.he...@gmail.com writes: Hello, Just curious of there's a way to set the tags in a region all at once? (org-map-entries (function org-set-tags) nil 'region) or (org-map-entries (lambda () (org-set-tags-to '(foo))) nil 'region) or some variation thereof. I did see that function, but it didn't DUI what I expected with M-x. Would u need to run it as above or could I use M-x with it somehow? A above I take it I'd put that in the buffer and then eval-region? John I see there's a way to do it via agenda, but I was curious if there was also a way to do it on a group of headlines from the buffer itself. In various google strategies, it looked like the answer was no. This is just a random file (making a camping packing/shopping list), so to do it via the way that seemed apparent was: C-c a to restrict to the file s to conduct a fake search that would just give all the headlines in the buffer highlight region : to set tags It would have just been easier to C-space on a region and set them in groups right from the buffer. I sort of expected something like C-u C-c C-c to set region tags? Thinking about it, I suppose since these happened to be tagged with :export:, I could have done an M-x replace-string and appended my additional tag. Thanks! John -- Nick
Re: [O] Export all headlines when some are set with :export:
On May 10, 2014 4:03 AM, Alexander Baier alexander.ba...@mailbox.org wrote: On 2014-05-10 05:11 John Hendy wrote: Hello, In creating a packing/buy list for an upcoming camping trip, I wanted two exports: - one for things to buy - one for everything on the list for packing If those two lists are disjoint, you can put each of them under its own subtree and export only the respective subtree. With point on the subtree to export press C-c C-e C-s toggeling the subtree export. Definitely. In this case, items were grouped functionally by cooking, activities, sleeping, etc. So there were both items we had and didn't in the same tree. Thanks, John HTH, -- Alexander Baier
Re: [O] org-ref code
On Thursday, 1 May 2014 at 13:07, John Kitchin wrote: I implemented some of this partially. I made it so you can specify the default cite link in a user variable, with a default of cite. When you type C-c ], this format will automatically be used. If you want to choose another format, type C-u C-c ] which will prompt you for a type, and then Hi John, I am having problems with org-ref and am obviously missing something trivial. I downloaded the latest version yesterday (Friday). You don't say, in the above, what function you actually bound to C-c ] but I bound org-ref-insert-cite-link and that doesn't seem to work: 1. C-u on it does not give me a choice of citation method 2. the link inserted looks like a link (it's blue) but there are actually no [[...]] characters surrounding it. What am I missing? Am I expected to type the [[]] or use C-c C-l? I would like to C-u C-c ], choose autocite and my refs and have your code insert [[autocite:blah-2001,joe-2010,moe-2014]] into my org buffer. I know I can change the default citation link type through org-ref-default-citation-link but I want the C-u functionality. Finally, looking at the code, it would appear that appending new citations will only work for cite: links as the cite: is hard-coded into the code? thanks again, eric PS - I'm a fellow Chemical Engineer but unfortunately have not yet had the opportunity to cite any of your papers but look forward to doing so sometime soon using org-ref ;-) -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-923-g233c11
Re: [O] Export to iCalendar only not DONE, scheduled tasks?
On Mon, May 5, 2014 at 11:08 PM, Arun Persaud apers...@lbl.gov wrote: pretty sure this can be done. I export only events to an ics file that have a start and an end date and are not in a certain category. For this I use That's great, thank you. I have this, but it doesn't work: (defun filter-scheduled-todo-tasks (content backend info) Filter iCalendar export to include only TODO tasks that are not done, but which are scheduled or have a deadline. (when (eq backend 'icalendar) (if (and (org-entry-is-todo-p) (not (org-entry-is-done-p)) (or (org-get-scheduled-time (point)) (org-get-deadline-time (point content nil))) ... called with: (let ((org-export-filter-final-output-functions '(filter-scheduled-todo-tasks))) (org-icalendar-combine-agenda-files)) I have (setq org-icalendar-include-todo t) too. Using edebug, it seems that the `content' argument only iterates through the top-level headings of each of my agenda files. I was assuming it'd iterate through each subheading too --- do I need to do this manually?
Re: [O] [ANN] Gnorb: Glue code between Gnus, Org, and BBDB
On 05/10/14 15:34 PM, Alan Schmitt wrote: On 2014-05-10 12:32, Eric Abrahamsen e...@ericabrahamsen.net writes: Alan Schmitt alan.schm...@polytechnique.org writes: [...] A more robust alternative than looking at the note's text could be to have a property with the link to the mail. (Later) I see that your LOGBOOK example uses a property to track the message. Could this be considered as the link? And I also see you only record the message id. How do you get to the right folder using it? But the link that should be replied to will change as the conversation progresses, that's why we're still scanning for links. But you're right, it might be a little safer to put the newest relevant message link in a property. Right now (this code hasn't been pushed yet), the GNORB_MSG_IDS property is used in the *other* direction: when you receive a message that might be relevant to a TODO (ie the second of the three mail functions I mentioned), the GNORB_MSG_IDS property is used to suggest the relevant TODO. We look at the IDs mentioned the References and In-Reply-To headers of the incoming mail, if any of those IDs appear in the GNORB_MSG_IDS property of a TODO, that TODO is suggested for state-change/completion. This doesn't do anything automatically, it's just used to suggest a likely default. [...] To follow a link, I don't simply click on it as it usually breaks my carefully crafted layout for my agenda and todo files. So I have a very simple function that creates a frame to display the link: #+begin_src emacs-lisp (defun as/copy-link-and-open-in-new-frame () (interactive) Copies the next link found and opens it in a new frame (org-next-link) (let ((link (org-element-property :raw-link (org-element-link-parser (make-frame '((name . follow-link))) (select-frame-by-name follow-link) (org-open-link-from-string link))) #+end_src This setup is why I'm so interested in gnorb: it's too much manual manipulation and friction. Yup, that looks like a pain. Right now gnorb saves window configuration when you handle a mail TODO, and restores it when the message is sent. But there are probably a lot of contingencies I haven't thought of, so it would be great to see how it works for you. Actually, the very first motivation for starting to work on these functions was annoyance at not being able to return properly from following a gnus link. [...] I'd like gnorb to do all the complicated bits for you. You should just be able to call whichever of the three functions is relevant, and then gnorb will put you in the right place, with a link loaded, to take a note or annotate a state-change. In the above example, `gnorb-org-handle-mail' should see that there are gnus links in the LOGBOOK, and start a reply to the most recent one. I know how to record state changes in the logbook (in the definition of `org-todo-keywords'), but I don't know how one adds notes. Do you do it by hand? Gnorb will give you the choice of triggering state change, or adding a note (with a customizable default, and a prefix arg to get the inverse). Usually, you can add a note manually with C-c C-z. A note won't affect `gnorb-org-handle-mail's behavior, it's just there for your information. In both cases, gnorb will leave you at the note message buffer, where you can insert a link or type whatever comments you want. [...] All this depends on you giving your BBDB records an org-tag field, which is pretty much the only file-format buy-in that Gnorb asks of you (I hope it remains the only one). Basic question: how does one add such a tag? I'm a very very basic user of bbdb, in the sense that I only use it to expand addresses when writing messages. I know it can do much more, but I don't know how. Sure: just hit i on a record, and it will prompt you to insert a field. The first time you use org-tags it will ask you to confirm you want to create a new field type; after that it will provide completion. Roland Winkler just made changes to the BBDB codebase that will allow us to store links to recently-received messages as an Xfield on each record, and I think that will be awesome (I happily stole this idea from org-contacts). It will also depend on people running the development version of BBDB, which will mean it will have a userbase of about four :) Such information would be useful, indeed. But you already provide a similar function with gnorb-bbdb-mail-search, don't you? I guess, yes, but redundancy is good! Sorry, this was a bit of a brain-dump. I think the issue of how people use email is fascinating, though, and I plan to look at software like Google Tasks or whatever, to collect some ideas. I'd love input from anyone with opinions! I also find the topic very interesting. Thanks again for your work! Alan
Re: [O] [ANN] Gnorb: Glue code between Gnus, Org, and BBDB
On 2014-05-10 18:36, Eric Abrahamsen e...@ericabrahamsen.net writes: Right now (this code hasn't been pushed yet), the GNORB_MSG_IDS property is used in the *other* direction: when you receive a message that might be relevant to a TODO (ie the second of the three mail functions I mentioned), the GNORB_MSG_IDS property is used to suggest the relevant TODO. We look at the IDs mentioned the References and In-Reply-To headers of the incoming mail, if any of those IDs appear in the GNORB_MSG_IDS property of a TODO, that TODO is suggested for state-change/completion. This doesn't do anything automatically, it's just used to suggest a likely default. Ah, very nice. I still think basing links on message ids is the most robust. I just gave a quick try and I can fairly easily find a message from an id through notmuch on the command line, or using an interactive search. I had a quick look at notmuch.el but I don't see a way to use it without a notmuch buffer, though. Actually, the very first motivation for starting to work on these functions was annoyance at not being able to return properly from following a gnus link. That's motivation enough! I know how to record state changes in the logbook (in the definition of `org-todo-keywords'), but I don't know how one adds notes. Do you do it by hand? Gnorb will give you the choice of triggering state change, or adding a note (with a customizable default, and a prefix arg to get the inverse). Usually, you can add a note manually with C-c C-z. A note won't affect `gnorb-org-handle-mail's behavior, it's just there for your information. In both cases, gnorb will leave you at the note message buffer, where you can insert a link or type whatever comments you want. Good to know, thanks. Basic question: how does one add such a tag? I'm a very very basic user of bbdb, in the sense that I only use it to expand addresses when writing messages. I know it can do much more, but I don't know how. Sure: just hit i on a record, and it will prompt you to insert a field. The first time you use org-tags it will ask you to confirm you want to create a new field type; after that it will provide completion. I'll give it a try. Thanks again, Alan
[O] new to drawers
I'm having trouble getting drawers to collapse, and am wondering if I'm misunderstanding their nature. I make an active region in an org-mode doc on, for instance, sample text and invoke C-c C-x d, which invites me to name the drawer. I name it test, and RET, which gives me: :test: sample text :END: :END: is colored green by org-mode, but test isn't. And it won't go through any kind of visibility cycle. I've tried [TAB] and shift+TAB, and shift+arrowkey, and don't get any response. Using emacs 24.3.1 and org 7.9.3f. What am I doing wrong? Thank you! steven arntson
Re: [O] Org version of texinfo manual
Achim Gratz writes:
I'm still in favor of doing this, but it will be an uphill battle. I'll
have to check what the state of my local branch is on this, let me get
back to you when it at least compiles the old version of the manual.
If you check out the orgmanual branch in Thomas' repository (and follow
the instructions on this list to integrate it into the Org build
system), then only these two patches are missing from my local version:
--8---cut here---start-8---
put back macros with problematic characters
Modified orgmanual.org
diff --git a/orgmanual.org b/orgmanual.org
index 0325614..ebe26ba 100644
--- a/orgmanual.org
+++ b/orgmanual.org
@@ -4254,13 +4254,10 @@ Priorities can be attached to any outline node; they do
not need to be TODO
items.
#+attr_texinfo: :table-type table :indic @asis
- - {{{kbd(C-c XXX)}}} ::
+ - {{{kbd(C-c \\,)}}} ::
-{{{kindex(C-c ,)}}}
-#+comment:{{{kindex(@kbd{C-c ,})}}}
-#+comment: Preceding line won't export to pdf
-{{{findex(org-priority)}}}
-#+comment: Should be C-c ,
+ {{{kindex(C-c \\,)}}}
+ {{{findex(org-priority)}}}
Set the priority of the current headline (~org-priority~). The
command prompts for a priority character {{{samp(A)}}}, {{{samp(B)}}}
@@ -9226,9 +9223,7 @@ the other commands, the cursor needs to be in the desired
line.
- ~\~ ~org-agenda-filter-by-tag-refine~ ::
- #+comment: {{{kindex(XXX)}}}
- #+comment: Should be \
- @@info:kindex \\@@
+ {{{kindex(\)}}}
Narrow the current agenda filter by an additional condition. When
called with prefix arg, remove the entries that /do/ have the tag, or
@@ -9350,11 +9345,9 @@ the other commands, the cursor needs to be in the
desired line.
Set tags for the current headline. If there is an active region in the
agenda, change a tag for all headings in the region.
-- {{{kbd(,)}}} ::
+- {{{kbd(\\,)}}} ::
- #+comment: {{{kindex(XXX)}}}
- #+comment: Should be a comma
- @@info:kindex ,@@
+ {{{kindex(\\,)}}}
Set the priority for the current item (~org-agenda-priority~). Org
mode prompts for the priority character. If you reply with
@@ -10691,12 +10684,9 @@ If you would like to see entities displayed as UTF8
characters, use the
following command:[fn:108]
#+attr_texinfo: :table-type table :indic @asis
-- @@info:@kbd{C-c C-x XXX}@@ ::
-
- #+comment: {{{kindex(C-c C-x XXX)}}}
- #+comment: Should be \
+- {{{kbd(C-c C-x \)}}} ::
- @@info:kindex C-c C-x \\
+ {{{kindex(C-c C-x \)}}}
Toggle display of entities as UTF-8 characters. This does not change
the buffer content which remains plain ASCII, but it overlays the
@@ -10740,9 +10730,7 @@ subscript, but ~a_{b}~ will.
#+attr_texinfo: :table-type table :indic @asis
- @@info:@kbd{C-c C-x \\}@@ ::
- #+comment: {{{kindex(C-c C-x XXX)}}}
- #+comment: Should be \
- @@info:@kindex C-c C-x \@@
+ {{{kindex(C-c C-x \)}}}
In addition to showing entities as UTF-8 characters, this command will
also format sub- and superscripts in a WYSIWYM way.
--8---cut here---end---8---
--8---cut here---start-8---
Makefile: put HTML manual into subfolder
Modified Makefile
diff --git a/Makefile b/Makefile
index 7c45664..fec57d6 100644
--- a/Makefile
+++ b/Makefile
@@ -34,7 +34,7 @@ orgmanual.pdf:LANG=C # work around a bug in
texi2dvi
orgmanual.pdf: orgmanual.texi
$(TEXI2PDF) $
orgmanual: orgmanual.texi
- $(TEXI2HTML) $
+ $(TEXI2HTML) $ -o $@
orgmanual.html: orgmanual.org
$(BEXP) $(EXHTML) $ $(ORG2HTML)
--8---cut here---end---8---
My addition to local.mk looks like this:
--8---cut here---start-8---
.PHONY: manclean orgmanual
EXTRADIRS=orgmanual
orgmanual:
$(MAKE) -C $@
manclean:
$(MAKE) -C orgmanual clean
clean: manclean
--8---cut here---end---8---
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] Export all headlines when some are set with :export:
On 2014-05-10 05:11 John Hendy wrote: Hello, In creating a packing/buy list for an upcoming camping trip, I wanted two exports: - one for things to buy - one for everything on the list for packing If those two lists are disjoint, you can put each of them under its own subtree and export only the respective subtree. With point on the subtree to export press C-c C-e C-s toggeling the subtree export. HTH, -- Alexander Baier
Re: [O] Set tags in region
On 2014-05-10 16:14 John Hendy wrote: On May 9, 2014 11:21 PM, Nick Dokos ndo...@gmail.com wrote: John Hendy jw.he...@gmail.com writes: Hello, Just curious of there's a way to set the tags in a region all at once? (org-map-entries (function org-set-tags) nil 'region) or (org-map-entries (lambda () (org-set-tags-to '(foo))) nil 'region) or some variation thereof. I did see that function, but it didn't DUI what I expected with M-x. Would u need to run it as above or could I use M-x with it somehow? A above I take it I'd put that in the buffer and then eval-region? If you want to call this interactively, i.e. via M-x or a key-binding, you will have to wrap this code in a defun with an interactive from and thus turn it into a command. Like this: #+BEGIN_SRC emacs-lisp (defun my-set-tag-in-region () (interactive) (org-map-entries (function org-set-tags) nil 'region)) #+END_SRC HTH, -- Alexander Baier
Re: [O] Set tags in region
Hello John, On 2014-05-10 04:53 John Hendy wrote: Just curious of there's a way to set the tags in a region all at once? I see there's a way to do it via agenda, but I was curious if there was also a way to do it on a group of headlines from the buffer itself. In various google strategies, it looked like the answer was no. This is just a random file (making a camping packing/shopping list), so to do it via the way that seemed apparent was: I often use (info (Emacs) Keyboard Macros) for situations like this. Define the macro with point at the beginning of a headline and then use `C-x C-k r' to execute it on every line in a region. [The (info ...) form above when evaluated takes you to the relevant page in the emacs manual.] HTH, -- Alexander Baier
Re: [O] new to drawers
At Sat, 10 May 2014 12:11:53 -0700, Steven Arntson wrote: I'm having trouble getting drawers to collapse, and am wondering if I'm misunderstanding their nature. I make an active region in an org-mode doc on, for instance, sample text and invoke C-c C-x d, which invites me to name the drawer. I name it test, and RET, which gives me: :test: sample text :END: :END: is colored green by org-mode, but test isn't. And it won't go through any kind of visibility cycle. I've tried [TAB] and shift+TAB, and shift+arrowkey, and don't get any response. Using emacs 24.3.1 and org 7.9.3f. What am I doing wrong? i can confirm this behaviour, it's the same over here. something is recognised as drawer if its name is either in the list 'org-drawers or defined in the current file with #+DRAWERS. try to add test either to org-drawers e.g. (setq org-drawers '(PROPERTIES CLOCK LOGBOOK RESULTS test2)) or add it to the file's headers: #+DRAWERS: HIDDEN STATE PROPERTIES BIG low and revert the buffer, if it's already open. as a hint: in my settings, a drawer is colored green. if you use an undefined string for a drawer name, it is white. so you quickly see, if your string is a defined drawer. and another, you can get completetions with TAB when you do C-c C-x d, your string should be in the list. kind regards, dieter
Re: [O] new to drawers
At Sun, 11 May 2014 00:38:15 +0200, Dieter Schoen wrote: e.g. (setq org-drawers '(PROPERTIES CLOCK LOGBOOK RESULTS test2)) or add it to the file's headers: #+DRAWERS: HIDDEN STATE PROPERTIES BIG low i shouldn't write emails after midnight.. the examples should read: (setq org-drawers '(PROPERTIES CLOCK LOGBOOK RESULTS test)) #+DRAWERS: HIDDEN STATE PROPERTIES test but i think you would have got the idea.. dieter
Re: [O] Questions about mail, MIME, etc.
One more follow-on question. When I run org-mime-org-buffer-htmlize, I get a buffer in message mode with a nice MIME message almost ready to go. I have not specified org-mime-library, so it defaults to mml, as expected for gnus. But when I type C-c C-c to send the message, I get prompted for via with three options (which I don't remember offhand, but it was something like 'transport', 'sendmail' and 'smtp'. However, if I had previously run and quit gnus in that session, it just sends the message, badda-boom-badda-bing. Is there some minimal configuration I can add to .emacs to have the effect of running and quitting gnus to messages will send? I realize this is not so much an org-mode question, but it's related. Thanks! -pd -- Peter Davis The Tech Curmudgeon www.techcurmudgeon.com
Re: [O] Questions about mail, MIME, etc.
Peter Davis p...@pfdstudio.com writes: One more follow-on question. When I run org-mime-org-buffer-htmlize, I get a buffer in message mode with a nice MIME message almost ready to go. I have not specified org-mime-library, so it defaults to mml, as expected for gnus. But when I type C-c C-c to send the message, I get prompted for via with three options (which I don't remember offhand, but it was something like 'transport', 'sendmail' and 'smtp'. However, if I had previously run and quit gnus in that session, it just sends the message, badda-boom-badda-bing. Is there some minimal configuration I can add to .emacs to have the effect of running and quitting gnus to messages will send? I realize this is not so much an org-mode question, but it's related. Thanks! -pd I have these variables set, I'll bet it's one or the other that makes the difference (probably the second). (setq mail-user-agent 'gnus-user-agent) (setq message-send-mail-function 'message-send-mail-with-sendmail)
[O] An org password manager
Hi! I have been using org for managing passwords for a some time now. In case someone is interested, the code is in: https://bitbucket.org/alfaromurillo/org-passwords.el To consult the database, the code provides a function to open the Org file with the passwords in Read-Only mode, sets a timer after which the buffer is killed and provides functions for copying the password without it getting into the kill-ring. It also provides two types of functions for generating passwords: strings of random characters, and random words of the correcthorsebatterystaple-type. The README file in bitbucket has detailed information about the usage. If there is interest from the community this can also go to /contrib. Best, Jorge.
Re: [O] new to drawers
Dieter Schoen die...@schoen.or.at writes: At Sun, 11 May 2014 00:38:15 +0200, Dieter Schoen wrote: e.g. (setq org-drawers '(PROPERTIES CLOCK LOGBOOK RESULTS test2)) or add it to the file's headers: #+DRAWERS: HIDDEN STATE PROPERTIES BIG low i shouldn't write emails after midnight.. the examples should read: (setq org-drawers '(PROPERTIES CLOCK LOGBOOK RESULTS test)) #+DRAWERS: HIDDEN STATE PROPERTIES test but i think you would have got the idea.. dieter Okay, I see--I thought you could just arbitrarily title them. Which would be a nice feature, IMHO! But this works fine for me, actually--for my use-case, it's fine to just use the predefined RESULTS title. Thank you! steven
Re: [O] An org password manager
jorge.a.alf...@gmail.com (Jorge A. Alfaro-Murillo) writes: Hi! I have been using org for managing passwords for a some time now. In case someone is interested, the code is in: https://bitbucket.org/alfaromurillo/org-passwords.el interesting. Thanks for sharing.
