Re: [O] bug: hovering window obscures text
On Tue, May 3, 2011 at 11:11, Jambunathan K wrote: > Aankhen writes: > >> On Mon, May 2, 2011 at 22:39, Samuel Wales wrote: >>> On this page >>> >>> http://orgmode.org/worg/org-faq.html#closing-outline-sections >>> >>> a hovering window in the upper right corner obscures text. >>> >>> This is possibly, but not necessarily, especially so when you use large >>> fonts. >>> >>> To reproduce, set the minimum font size in Firefox to the largest >>> available setting. >>> >>> I wonder if a non-hovering solution is possible? I know we discussed >>> this before at one point, with several good designs. >> >> I’m not familiar with the prior discussions. The current design seems >> okay to me—notwithstanding the flaw you mention—because it strikes a >> good balance between making the TOC easily accessible and minimizing >> the amount of space it takes up. Of course, this is predicated on the >> assumption that people actually want to use the TOC, and often enough >> to justify it taking up that space. > > Considering that Samuel is making his argument from accessibility > perspective, "Accessibility" is one another predicate that is missing in > your assumption. I’m not sure how accessibility is hindered, given that the contents of the page are still perfectly accessible. All the fixed TOC does is obscure a very small portion of them on occasion, which can be rectified by scrolling. I would call that inconvenient, not inaccessible. Unless there’s more happening here beyond what I’ve seen, that is. Aankhen
Re: [O] bug: hovering window obscures text
Aankhen writes: > On Mon, May 2, 2011 at 22:39, Samuel Wales wrote: >> On this page >> >> http://orgmode.org/worg/org-faq.html#closing-outline-sections >> >> a hovering window in the upper right corner obscures text. >> >> This is possibly, but not necessarily, especially so when you use large >> fonts. >> >> To reproduce, set the minimum font size in Firefox to the largest >> available setting. >> >> I wonder if a non-hovering solution is possible? I know we discussed >> this before at one point, with several good designs. > > I’m not familiar with the prior discussions. The current design seems > okay to me—notwithstanding the flaw you mention—because it strikes a > good balance between making the TOC easily accessible and minimizing > the amount of space it takes up. Of course, this is predicated on the > assumption that people actually want to use the TOC, and often enough > to justify it taking up that space. Considering that Samuel is making his argument from accessibility perspective, "Accessibility" is one another predicate that is missing in your assumption. Jambunathan K. > > Meanwhile, for a quick fix, try this user style: > > http://userstyles.org/styles/47418/worg-disable-fixed-toc > > Aankhen > > --
Re: [O] bug: hovering window obscures text
On Mon, May 2, 2011 at 22:39, Samuel Wales wrote: > On this page > > http://orgmode.org/worg/org-faq.html#closing-outline-sections > > a hovering window in the upper right corner obscures text. > > This is possibly, but not necessarily, especially so when you use large fonts. > > To reproduce, set the minimum font size in Firefox to the largest > available setting. > > I wonder if a non-hovering solution is possible? I know we discussed > this before at one point, with several good designs. I’m not familiar with the prior discussions. The current design seems okay to me—notwithstanding the flaw you mention—because it strikes a good balance between making the TOC easily accessible and minimizing the amount of space it takes up. Of course, this is predicated on the assumption that people actually want to use the TOC, and often enough to justify it taking up that space. Meanwhile, for a quick fix, try this user style: http://userstyles.org/styles/47418/worg-disable-fixed-toc Aankhen
Re: [O] insert picture feature request.
Thanks. It is what I need. Than On Mon, May 2, 2011 at 4:23 PM, brian powell wrote: > * This is what I use (thanks to whomever wrote the original): > > (defun org-screenshot () > "Take a screenshot into a time stamped > unique-named file in the same directory as the org-buffer and insert a > link to this file." > (interactive) > (setq filename > (concat > (make-temp-name > (concat (buffer-file-name) > "_" > (format-time-string > "%Y%m%d_%H%M%S_")) ) ".png")) > (call-process "import" nil nil nil filename) > (insert (concat "[[" filename "]]"))) > > ** Works great for me, puts a timestamp on it and the filename. > > ** Also, notice the ".png": > > *** The link above suggests ".jpg" (as the default)--which is great > for most things; except, JPG is a lossy compression format, but it > does load faster. > > http://www.turnkeylinux.org/blog/png-vs-jpg > >
[O] Bury (or kill) calendar buffer after selecting a date
Hi list, A while ago someone (I'm sorry, I don't remember who, now) proposed a patch that the *Calendar* buffer could be buried after selecting a date. I thought it was a great idea, and I've implemented a simple advice in my .emacs that accomplishes the same thing. I'm posting it here on the chance that someone else might find it useful. The problem this solves is that after you enter a date, the calendar buffer is next in line in the buffer ring, so you will switch to it next by default, instead of the buffer you were working with previously. This advice will kill the calendar buffer after entering a date (I never need it around anyway), but you could just as easily bury-buffer, which would move it to the back of the ring. -Anthony ; defadvice to kill the calendar buffer after selecting a date, so it is out of ; the way (defadvice org-read-date (after abl/kill-calendar-after-org-read-date (&optional with-time to-time from-string prompt default-time efault-input) protect) "kill the *Calendar* buffer after reading a date" (kill-buffer "*Calendar*")) (ad-activate 'org-read-date)
Re: [O] org-capture-other-frame
Hi LLuis, Thanks for sharing, this looks really interesting. Could you give us a bit more information on how you are using it (how you are setting up the hotkeys, what's the workflow, etc)? Some specs about your system would help as well. I'm using OSX 10.6. Cheers! Marcelo. On Mon, May 2, 2011 at 1:07 PM, Lluís wrote: > I've made a little function to launch org-capture on another frame, > which is very handy when plugged into a hotkey and working with other > applications. > > It lacks some settings that I already have active system wide (like no > scrollbars, no toolbar and the like), so you should probably tune those > (a defcustom for the frame parameters should suffice). > > In any case, tell me (directly, as I'm not not subscribed) if you're > going to install this into org-mode. Otherwise I'll upload the snippet > into emacs wiki: > > #+begin_src lisp > (defun my-org-capture-other-frame () > "Create a new frame and run org-capture." > (interactive) > (make-frame '((name . "Org-Capture") > (width . 120) > (height . 20) > (menu-bar-lines . 0) > (tool-bar-lines . 0) > (auto-lower . nil) > (auto-raise . t))) > (select-frame-by-name "Org-Capture") > (if (condition-case nil > (progn (org-capture) t) > (error nil)) > (delete-other-windows) > (my-org-capture-other-frame-cleanup))) > > (defun my-org-capture-other-frame-cleanup () > "Close the Org-Capture frame." > (if (equal "Org-Capture" (frame-parameter nil 'name)) > (delete-frame))) > (add-hook 'org-capture-after-finalize-hook > 'my-org-capture-other-frame-cleanup) > #+end_src > > > Thanks, > Lluis > > -- > "And it's much the same thing with knowledge, for whenever you learn > something new, the whole world becomes that much richer." > -- The Princess of Pure Reason, as told by Norton Juster in The Phantom > Tollbooth > >
Re: [O] Backuping org with git, cron and Dropbox
Hi Theo, Thanks for the tip. I don't really program in bash, so that was a useful tip. I'll start getting into it more, as it's a simple and powerful way to solve problems, and it's available almost everywhere you have a POSIX OS :) Cheers, Marcelo. On Mon, May 2, 2011 at 12:16 PM, theo wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > > > On 01/05/2011 07:36, Marcelo de Moraes Serpa wrote: >> >> 1 DAYW=$(date | cut -d" " -f 1) >> 2 NOW=$(date +"%d-%m-%Y-%r") >> [...] >> 6 git commit -a -m "$DAYW-$NOW" > > Could be shorten : > 6 git commit -a -m "$(date +'%A-%F-%T')" > > - -- > Freeely, > theo > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJNvubRAAoJECkgngj8k9Tvn+UH/1wv5z7Z5sLjBMuxERkZlSsi > 8yPGbRyg6TgVXUjNAseOSoDeYPfj83cz+DF1mX7A9xz1GPfW+M38lWyNR2ALFL75 > 0/V5X40Yz9RuLb06CoilVH7xUu7SEbTHbSEjjwnZIj6WeKAhalucWR0L0ZoWbE5K > 54lxfrzm+VcVZI3eD1AuROjoEgf+OZFc24qFqEepeH6cVydUEuRnNXVVfIxq7XDN > IyF1wXkmqvWgX9FKuRY4XNM62z4UZBDj/Pwvt/vhJA64tK43d8By6N/vmwQJu3a+ > iS0+xLPV2ud5t7bQ8Cz1nxQJ4lsBwBfJhQhIIfbWBeq+tULE5Fo+w/iixQn8UI8= > =GQrM > -END PGP SIGNATURE- > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > >
[O] PERL, org-mode and literal document input.
Greetings.
I've got a YAML config file and some processing I'm doing to it. I'd
love to have both the bits inside the maintenance document I'm writing
to manage a service. This seems a perfect use for code blocks and their
evaluation. However, I get behavior out of my attempt to do this which
I find strange.
I include a minimal, failing example below.
The problem "appears" to be somewhere in the :var reference designed to
introduce the other code block. There are two problems, one pretty
egregious, the other somewhat subtle.
Egregious first:
For some reason, whatever process sucks up config_yml and inserts it
into '$config' in mogrify_pl just elides the first two lines.
Additionally, the contents of the variable are very strangely
formatted. The contents of most of the first YAML document (less the
first two lines) are each on a separate line.
However, the last of the first doc and all of the second doc are in a
single line.
Subtle:
The last few newlines are also elided. This might not seem to be a big
deal, but YAML really wants to end with a trailing newline. I figure I
should be able to express that in the doc, and not tag one on in my
code.
...
If I add a #+begin_src line to config_yml, and then build a results
section by hand, and copy the identical document there, then the
variable is imported more or less as I'd expect: $config is one large
scalar value, with the contents of config_yml inserted. The trailing
newlines are still stripped, but this is better at least.
I've been searching for something like "Echo this" to put in my
begin_src; it would seem a little silly but not awful to define a
process to just copy the contents of the source block to the result, and
go from there. But it's inelegant, to say the least.
...
So: Is there a conventional way I should get org to treat the source
block 'the same way' it treats the results block? Failing that, is
there a common idiom to run a source block to get the result "Echo me
verbatim into the results block" ?
I see profligate use of org-babel-trim in the code. Does that mean that
permitting leading or trailing whitespace is a regular source of
problems? I didn't want to start dinking with it casually.
...
Any pointers would be deeply appreciated.
*** YAML transform.
#+srcname: config_yml
---
erpalpha:
- alpha-rac-1.erp.ufl.edu
- alpha-rac-2.erp.ufl.edu
erpbeta:
- beta-rac-1.erp.ufl.edu
- beta-rac-2.erp.ufl.edu
---
erpalpha:
FS: /export/alpha
nodes:
erpalpha: ''
erpbeta: RO
erpbeta:
FS: /export/beta
nodes:
erpalpha: RO
erpbeta:
#+end_src
#+srcname: mogrify_pl
#+begin_src perl :results output :var config=config_yml()
use YAML();
use Data::Dumper;
# $stream = join("",<$foo>);
print "===$config===\n";
print $#config,"\n";
foreach $line (@{$config})
{ print "[$line]\n"; }
print Dumper($config);
# ($nodegroups,$filespaces) = YAML::Load($config);
# print YAML::Dump($nodegroups,$filespaces);
#+end_src
#+results: mogrify_pl
#+begin_example
===ARRAY(0x853b818)===
-1
[alpha-rac-1.erp.ufl.edu]
[alpha-rac-2.erp.ufl.edu
erpbeta:]
[beta-rac-1.erp.ufl.edu]
[beta-rac-2.erp.ufl.edu
---
erpalpha:
FS: /export/alpha
nodes:
erpalpha: ''
erpbeta: RO
erpbeta:
FS: /export/beta
nodes:
erpalpha: RO
erpbeta:]
$VAR1 = [
'alpha-rac-1.erp.ufl.edu',
'alpha-rac-2.erp.ufl.edu
erpbeta:',
'beta-rac-1.erp.ufl.edu',
'beta-rac-2.erp.ufl.edu
---
erpalpha:
FS: /export/alpha
nodes:
erpalpha: \'\'
erpbeta: RO
erpbeta:
FS: /export/beta
nodes:
erpalpha: RO
erpbeta:'
];
#+end_example
- Allen S. Rout
[O] org-capture-other-frame
I've made a little function to launch org-capture on another frame, which is very handy when plugged into a hotkey and working with other applications. It lacks some settings that I already have active system wide (like no scrollbars, no toolbar and the like), so you should probably tune those (a defcustom for the frame parameters should suffice). In any case, tell me (directly, as I'm not not subscribed) if you're going to install this into org-mode. Otherwise I'll upload the snippet into emacs wiki: #+begin_src lisp (defun my-org-capture-other-frame () "Create a new frame and run org-capture." (interactive) (make-frame '((name . "Org-Capture") (width . 120) (height . 20) (menu-bar-lines . 0) (tool-bar-lines . 0) (auto-lower . nil) (auto-raise . t))) (select-frame-by-name "Org-Capture") (if (condition-case nil (progn (org-capture) t) (error nil)) (delete-other-windows) (my-org-capture-other-frame-cleanup))) (defun my-org-capture-other-frame-cleanup () "Close the Org-Capture frame." (if (equal "Org-Capture" (frame-parameter nil 'name)) (delete-frame))) (add-hook 'org-capture-after-finalize-hook 'my-org-capture-other-frame-cleanup) #+end_src Thanks, Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
02/05/11 17:22, Matt Lundin
> Antoine Levitt writes:
>
> [...]
>
>> Alright, so I did that, and I seem to have encountered an org-mode
>> bug. Put this in .emacs
>>
>> (setq
>> org-agenda-skip-scheduled-if-done t
>> org-agenda-custom-commands
>> '(("l" "Agenda with done items"
>> agenda "" ((org-agenda-skip-scheduled-if-done nil)
>>
>> (define-key org-agenda-mode-map (kbd "l") (lambda () (interactive)
>> (org-agenda nil "l")
>>
>> M-x org-agenda a -> displays only TODO items, which is fine.
>> l -> display of DONE items also, which is also fine.
>> q -> quits org-agenda
>> M-x org-agenda a -> still fine
>> M-x org-agenda b/f -> also displays DONE items, which is a bug
>
> I cannot reproduce this. What version of org-mode are you using?
>
> - Matt
Right, sorry, I was using org-agenda-list. Here are the updated
instructions
M-x org-agenda a -> displays only TODO items, which is fine.
l -> display of DONE items also, which is also fine.
q -> quits org-agenda
M-x org-agenda-list -> still fine
b/f -> also displays DONE items
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
02/05/11 14:07, Carsten Dominik > On May 2, 2011, at 11:52 AM, Antoine Levitt wrote: > >> 02/05/11 11:20, Carsten Dominik >>> Hi Antoine, >> >> Hi, thanks for replying to this old thread. >> >>> the agenda does list scheduled items anyway, so I do not see why >>> this information should be repeated in the logging items. >> >> It doesn't list DONE scheduled items. The point is I'd like for log-mode >> to be just like the normal agenda, except that it also lists DONE items. >> >> I think maybe log should just force org-agenda-skip-scheduled-if-done >> to t. > > > I don't really think so. A Scheduling timestamp, or a Deadline are for > planning. > The log view is for displaying when things where actually done. Alright. It makes more sense for me to display a log view of when things were planned, because I often close TODOs either before or after the actual event. But I guess that's just my use. > > AA work-around for you is to make a custom agenda view and set > org-agenda-skip-scheduled-if-done in the options section of > that custom command Seems sensible, I'll do that, thanks! > > - Carsten > >> That'd make sense, wouldn't it? Or maybe I'm just extrapolating my >> own use case too much, I don't know enough about org usage patterns to >> be sure. But I do know that I'd like a function to review my past >> appointments/timed todos.
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
02/05/11 11:20, Carsten Dominik > Hi Antoine, Hi, thanks for replying to this old thread. > the agenda does list scheduled items anyway, so I do not see why > this information should be repeated in the logging items. It doesn't list DONE scheduled items. The point is I'd like for log-mode to be just like the normal agenda, except that it also lists DONE items. I think maybe log should just force org-agenda-skip-scheduled-if-done to t. That'd make sense, wouldn't it? Or maybe I'm just extrapolating my own use case too much, I don't know enough about org usage patterns to be sure. But I do know that I'd like a function to review my past appointments/timed todos.
Re: [O] [PATCH 4/4] Add helper functions to org-bibtex
Hi Matt, These last two patches are now applied. Many Thanks. Now I just have to figure out how to use tags, so I can organize my reading by tag/keyword... Cheers -- Eric Matt Lundin writes: > Hi Eric, > > "Eric Schulte" writes: > >> Hi Matt, >> >> Thanks for these patches, they all look great. > > Thanks for applying them. I'm really excited about this new > functionality; it's exactly what I had been looking for. > > Thanks for implementing it in the first place! > >> >> I've just applied the first three, however this last patch does not >> apply to the current head. For example the first chunk alters a >> variable named `org-bibtex-treat-headline-as-title' which does not exist >> in the current git head. Perhaps you are missing an intervening patch? > > Sorry. It was against an earlier patch I had sent but forgot to cc you > on: > > http://patchwork.newartisans.com/patch/773/ > > Best, > Matt > -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] Old versions
What's the oldest version of org-mode known to work with Gnu Emacs 21.4.1? And where can I find a copy? (In this particular case, that's the emacs version on my cheap shared-hosting web account.) -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info
Re: [O] Backuping org with git, cron and Dropbox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, On 01/05/2011 07:36, Marcelo de Moraes Serpa wrote: > > 1 DAYW=$(date | cut -d" " -f 1) > 2 NOW=$(date +"%d-%m-%Y-%r") > [...] > 6 git commit -a -m "$DAYW-$NOW" Could be shorten : 6 git commit -a -m "$(date +'%A-%F-%T')" - -- Freeely, theo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNvubRAAoJECkgngj8k9Tvn+UH/1wv5z7Z5sLjBMuxERkZlSsi 8yPGbRyg6TgVXUjNAseOSoDeYPfj83cz+DF1mX7A9xz1GPfW+M38lWyNR2ALFL75 0/V5X40Yz9RuLb06CoilVH7xUu7SEbTHbSEjjwnZIj6WeKAhalucWR0L0ZoWbE5K 54lxfrzm+VcVZI3eD1AuROjoEgf+OZFc24qFqEepeH6cVydUEuRnNXVVfIxq7XDN IyF1wXkmqvWgX9FKuRY4XNM62z4UZBDj/Pwvt/vhJA64tK43d8By6N/vmwQJu3a+ iS0+xLPV2ud5t7bQ8Cz1nxQJ4lsBwBfJhQhIIfbWBeq+tULE5Fo+w/iixQn8UI8= =GQrM -END PGP SIGNATURE- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
[O] bug: hovering window obscures text
On this page http://orgmode.org/worg/org-faq.html#closing-outline-sections a hovering window in the upper right corner obscures text. This is possibly, but not necessarily, especially so when you use large fonts. To reproduce, set the minimum font size in Firefox to the largest available setting. I wonder if a non-hovering solution is possible? I know we discussed this before at one point, with several good designs. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html I support the Whittemore-Peterson Institute (WPI) === I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.
Re: [O] [PATCH 4/4] Add helper functions to org-bibtex
Hi Eric, "Eric Schulte" writes: > Hi Matt, > > Thanks for these patches, they all look great. Thanks for applying them. I'm really excited about this new functionality; it's exactly what I had been looking for. Thanks for implementing it in the first place! > > I've just applied the first three, however this last patch does not > apply to the current head. For example the first chunk alters a > variable named `org-bibtex-treat-headline-as-title' which does not exist > in the current git head. Perhaps you are missing an intervening patch? Sorry. It was against an earlier patch I had sent but forgot to cc you on: http://patchwork.newartisans.com/patch/773/ Best, Matt
Re: [O] Collaboration and settings --- was Re: bug in latex export tutorial?
Aloha Robert,
I think this is an important issue. I haven't seen it addressed fully.
There was a discussion on the mailing list a while back on how the
complexity of configuration made org-mode difficult to adopt. This
resulted in the short version of the manual, but not much in the way
of configuration strategies, IIRC.
Something similar came up in the context of using buffer local
variables to configure export parameters on a per-document basis. I'm
not a programmer, but your solution looks similar to me.
Programmers on the list might have a different take on this, but my
sense is that the complexity of configuration has so far frustrated
attempts to bring it under firmer control.
All the best,
Tom
On May 1, 2011, at 6:12 AM, Robert Goldman wrote:
On 4/30/11 Apr 30 -5:14 PM, Eric S Fraga wrote:
Robert Goldman writes:
On 4/29/11 Apr 29 -1:21 PM, Nick Dokos wrote:
[...]
amsmath conflicts with wasysym (redefines \iint), so you have to
redefine your headers to omit wasysym or include amsmath *first*:
for
some reason, if you \usepackage{amsmath} *before* you
\usepackage{wasysym}, the error does not arise -- presumably,
amsmath
assumes that \iint is not defined beforehand, whereas wasysym
does not
make that assumption.
The not-very-tasty solution I came up with was to put the
following into
the local variables list at the foot of my file:
# org-export-latex-default-packages-alist: (("AUTO" "inputenc" t)
("T1"
"fontenc" t) ("" "fixltx2e" nil) ("" "graphicx" t) ("" "longtable"
nil)
("" "float" nil) ("" "wrapfig" nil) ("" "soul" t) ("" "t1enc" t) (""
"textcomp" t) ("" "marvosym" t) ("" "amsmath" t) ("" "wasysym" t)
(""
"latexsym" t) ("" "amssymb" t)
("colorlinks
=true,pdfstartview=FitV,linkcolor=blue,citecolor=blue,urlcolor=blue"
"hyperref" nil) "\\tolerance=1000")
I put this in the file, rather than in my configuration, because
it is
specific to the formatting of this file, and because I share this
document with others, who need to be able to export from it w/o
having
to reconfigure their org-mode installations.
I figure that someone can probably suggest a solution that is
nicer than
that!
Best,
r
From earlier this year on the mailing list, below is a solution
which works if you more often than not want amsmath; i.e. it's not a
solution for the use case you specify in which you want to share a
single file etc. However, it's worth repeating this solution for
other
use cases.
Is there any documentation any where about how people use Org-mode in
collaborative authoring? I find myself not on solid ground
understanding how to ensure that my colleagues have the same
configuration. For now, I resort to entries in the local variables
list, but this may not be the best solution
One could hijack the directory locals, but that seems like The Wrong
Thing --- we should leave that to the individual user for his/her
preferences. Possibly set up something that would be layered, so that
there are dir-locals that optionally load user-specific settings /
after/
the dir-locals (i.e., a second layer of dir-locals)?
Is anyone else trying to do stuff like this?
best,
r
[O] CUSTOM_ID only works when entire file is exported?
I'm using C-c e b to do an HTML export. It appears that CUSTOM_ID only gets assigned when the entire file (not just the tagged sub-heading/tree) gets exported. The same goes for the HTML_CONTAINER_CLASS variable, only its worse because it will sometimes prevent export altogether with a "Before first headline at position xx in buffer org-mode-tmp" message, which I have no idea what it means. Is there anyway to export just one sub-tree (or heading group) with an assigned custom_id? Thanks, Mark
Re: [O] [PATCH] org-bibtex, add crossref option to bibtex incollection
Hi Tom, Thanks for sharing these updates, I've just applied them. Best -- Eric "Thomas S. Dye" writes: > Aloha all, > > Org-bibtex is working out nicely. The crossref field was defined in > org-bibtex, but not used. > > The attached patches add the crossref field to reference types that > might use it. > > All the best, > Tom > > > > > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [PATCH 4/4] Add helper functions to org-bibtex
Hi Matt, Thanks for these patches, they all look great. I've just applied the first three, however this last patch does not apply to the current head. For example the first chunk alters a variable named `org-bibtex-treat-headline-as-title' which does not exist in the current git head. Perhaps you are missing an intervening patch? Thanks! -- Eric Matt Lundin writes: > * lisp/org-bibtex.el: (org-bibtex-search): New function. > (org-bibtex-export-to-kill-ring): New function. Export to kill ring. > (org-bibtex-create-in-current-entry): New function > (org-bibtex-create): Make it easier to add bib fields to an > existing headline > (org-bibtex-export-arbitrary-fields) > (org-bibtex-treat-headline-as-title): Fix typos > (org-bibtex-fleshout): Don't upcase optional field; remove ":" from > type completion > > This patch implements several helper functions: exporting to kill > ring, searching only for entries with bib fields, and creating bib > fields in an existing headline. It makes the UI of org-bibtex-fleshout > more consistent. > --- > lisp/org-bibtex.el | 51 --- > 1 files changed, 40 insertions(+), 11 deletions(-) > > diff --git a/lisp/org-bibtex.el b/lisp/org-bibtex.el > index 513519b..868535d 100644 > --- a/lisp/org-bibtex.el > +++ b/lisp/org-bibtex.el > @@ -226,14 +226,14 @@ For example setting to 'BIB_' would allow > interoperability with fireforg." > (defcustom org-bibtex-treat-headline-as-title t >"Treat headline text as title if title property is absent. > If an entry is missing a title property, use the headline text as > -the property. If this value is t, `org-bibtex-check` will ignore > +the property. If this value is t, `org-bibtex-check' will ignore > a missing title field." >:group 'org-bibtex >:type 'boolean) > > (defcustom org-bibtex-export-arbitrary-fields nil >"When converting to bibtex allow fields not defined in `org-bibtex-fields'. > -This only has effect if org-bibtex-prefix is defined, so as to > +This only has effect if `org-bibtex-prefix' is defined, so as to > ensure that other org-properties, such as CATEGORY or LOGGING are > not placed in the exported bibtex entry." >:group 'org-bibtex > @@ -385,7 +385,7 @@ This variable is relevant only if > `org-bibtex-export-tags-as-keywords` is t." > With optional argument OPTIONAL, also prompt for optional fields." >(flet ((val (key lst) (cdr (assoc key lst))) >(keyword (name) (intern (concat ":" (downcase name > - (name (keyword) (upcase (substring (symbol-name keyword) 1 > + (name (keyword) (substring (symbol-name keyword) 1))) > (dolist (field (append > (if org-bibtex-treat-headline-as-title > (remove :title (val :required (val type > org-bibtex-types))) > @@ -530,22 +530,36 @@ With prefix argument OPTIONAL also prompt for optional > fields." > With prefix argument OPTIONAL also prompt for optional fields." >(interactive) (org-map-entries (lambda () (org-bibtex-check optional > > -(defun org-bibtex-create (&optional arg) > - "Create a new entry at the given level." > +(defun org-bibtex-create (&optional arg nonew) > + "Create a new entry at the given level. > +With a prefix arg, query for optional fields as well. > +If nonew is t, add data to the headline of the entry at point." >(interactive "P") >(let* ((type (org-icompleting-read > - "Type: " (mapcar (lambda (type) (symbol-name (car type))) > - org-bibtex-types))) > - (type (if (keywordp type) type (intern type > + "Type: " (mapcar (lambda (type) > +(substring (symbol-name (car type)) 1)) > + org-bibtex-types) > + nil nil (when nonew (org-bibtex-get "TYPE" > + (type (if (keywordp type) type (intern (concat ":" type > + (org-bibtex-treat-headline-as-title (if nonew nil t))) > (unless (assoc type org-bibtex-types) >(error "type:%s is not known" type)) > -(org-insert-heading) > -(let ((title (org-bibtex-ask :title))) > - (insert title) (org-bibtex-put "TITLE" title)) > +(if nonew > + (org-back-to-heading) > + (org-insert-heading) > + (let ((title (org-bibtex-ask :title))) > + (insert title) > + (org-bibtex-put "TITLE" title))) > (org-bibtex-put "TYPE" (substring (symbol-name type) 1)) > (org-bibtex-fleshout type arg) > (mapc (lambda (tag) (org-toggle-tag tag t)) org-bibtex-tags))) > > +(defun org-bibtex-create-in-current-entry (&optional arg) > + "Add bibliographical data to the current entry. > +With a prefix arg, query for optional fields." > + (interactive "P") > + (org-bibtex-create arg t)) > + > (defun org-bibtex-read () >"Read a bibtex entry and save to `*org-bibtex-entries*'. > This uses `bibtex-parse-entry'." > @@ -608,6 +622,21 @@ This uses `bi
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
Antoine Levitt writes:
> 02/05/11 17:22, Matt Lundin
>> Antoine Levitt writes:
>>
>> [...]
>>
>>> Alright, so I did that, and I seem to have encountered an org-mode
>>> bug. Put this in .emacs
>>>
>>> (setq
>>> org-agenda-skip-scheduled-if-done t
>>> org-agenda-custom-commands
>>> '(("l" "Agenda with done items"
>>> agenda "" ((org-agenda-skip-scheduled-if-done nil)
>>>
>>> (define-key org-agenda-mode-map (kbd "l") (lambda () (interactive)
>>> (org-agenda nil "l")
>>>
>>> M-x org-agenda a -> displays only TODO items, which is fine.
>>> l -> display of DONE items also, which is also fine.
>>> q -> quits org-agenda
>>> M-x org-agenda a -> still fine
>>> M-x org-agenda b/f -> also displays DONE items, which is a bug
>>
>> I cannot reproduce this. What version of org-mode are you using?
>>
>> - Matt
>
> Right, sorry, I was using org-agenda-list. Here are the updated
> instructions
>
> M-x org-agenda a -> displays only TODO items, which is fine.
> l -> display of DONE items also, which is also fine.
> q -> quits org-agenda
> M-x org-agenda-list -> still fine
> b/f -> also displays DONE items
I can confirm this bug with this latter set of instructions, though I'm
puzzled why M-x org-agenda-list behaves differently than C-c a a.
Best,
Matt
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
Antoine Levitt writes:
[...]
> Alright, so I did that, and I seem to have encountered an org-mode
> bug. Put this in .emacs
>
> (setq
> org-agenda-skip-scheduled-if-done t
> org-agenda-custom-commands
> '(("l" "Agenda with done items"
> agenda "" ((org-agenda-skip-scheduled-if-done nil)
>
> (define-key org-agenda-mode-map (kbd "l") (lambda () (interactive)
> (org-agenda nil "l")
>
> M-x org-agenda a -> displays only TODO items, which is fine.
> l -> display of DONE items also, which is also fine.
> q -> quits org-agenda
> M-x org-agenda a -> still fine
> M-x org-agenda b/f -> also displays DONE items, which is a bug
I cannot reproduce this. What version of org-mode are you using?
- Matt
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
02/05/11 14:07, Carsten Dominik
> On May 2, 2011, at 11:52 AM, Antoine Levitt wrote:
>
>> 02/05/11 11:20, Carsten Dominik
>>> Hi Antoine,
>>
>> Hi, thanks for replying to this old thread.
>>
>>> the agenda does list scheduled items anyway, so I do not see why
>>> this information should be repeated in the logging items.
>>
>> It doesn't list DONE scheduled items. The point is I'd like for log-mode
>> to be just like the normal agenda, except that it also lists DONE items.
>>
>> I think maybe log should just force org-agenda-skip-scheduled-if-done
>> to t.
>
>
> I don't really think so. A Scheduling timestamp, or a Deadline are for
> planning.
> The log view is for displaying when things where actually done.
>
> AA work-around for you is to make a custom agenda view and set
> org-agenda-skip-scheduled-if-done in the options section of
> that custom command
Alright, so I did that, and I seem to have encountered an org-mode
bug. Put this in .emacs
(setq
org-agenda-skip-scheduled-if-done t
org-agenda-custom-commands
'(("l" "Agenda with done items"
agenda "" ((org-agenda-skip-scheduled-if-done nil)
(define-key org-agenda-mode-map (kbd "l") (lambda () (interactive) (org-agenda
nil "l")
M-x org-agenda a -> displays only TODO items, which is fine.
l -> display of DONE items also, which is also fine.
q -> quits org-agenda
M-x org-agenda a -> still fine
M-x org-agenda b/f -> also displays DONE items, which is a bug
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
Hi, Carsten Dominik wrote: > On May 2, 2011, at 11:52 AM, Antoine Levitt wrote: >> 02/05/11 11:20, Carsten Dominik >>> Hi Antoine, >> >> Hi, thanks for replying to this old thread. >> >>> the agenda does list scheduled items anyway, so I do not see why >>> this information should be repeated in the logging items. >> >> It doesn't list DONE scheduled items. The point is I'd like for log-mode >> to be just like the normal agenda, except that it also lists DONE items. >> >> I think maybe log should just force org-agenda-skip-scheduled-if-done >> to t. > > I don't really think so. A Scheduling timestamp, or a Deadline are for > planning. > The log view is for displaying when things where actually done. > > AA work-around for you is to make a custom agenda view and set > org-agenda-skip-scheduled-if-done in the options section of > that custom command I would add that you can see what you did by displaying *logged* entries, ie a report based on the time you really spent doing something last week. Best regards, Seb -- Sébastien Vauban
Re: [O] insert picture feature request.
* This is what I use (thanks to whomever wrote the original): (defun org-screenshot () "Take a screenshot into a time stamped unique-named file in the same directory as the org-buffer and insert a link to this file." (interactive) (setq filename (concat (make-temp-name (concat (buffer-file-name) "_" (format-time-string "%Y%m%d_%H%M%S_")) ) ".png")) (call-process "import" nil nil nil filename) (insert (concat "[[" filename "]]"))) ** Works great for me, puts a timestamp on it and the filename. ** Also, notice the ".png": *** The link above suggests ".jpg" (as the default)--which is great for most things; except, JPG is a lossy compression format, but it does load faster. http://www.turnkeylinux.org/blog/png-vs-jpg
Re: [O] Org minor mode in mail-mode
> >> Any idea on how to make use of org minor mode in mail-mode and still > >> be able to fill-paragraph without impacting mail headers? > > > > The org minor modes set the local value of fill-paragraph-function to > > org-fill-paragraph. You can override this by adding a line to your hook > > function: > > > > (defun turn-on-full-org-mailing () > > (turn-on-orgstruct++) > > (turn-on-orgtbl) > > (load "org-html-mail") > > (setq fill-paragraph-function 'message-fill-paragraph)) > > > > I'm not sure how this will affect calling fill on lists or tables, > > however. As matter of fact, the trouble comes from `turn-on-orgstruct++'. Using `turn-on-orgstruct' instead is alright. When called `fill-paragraph' operates without interfering with the mail header. > Another idea would be to change `paragraph-start' and > `paragraph-separate' values when turning on orgstruct and orgtbl. Does not seem to work for me. -- Rene
Re: [O] headings with begin/end markers
bertie writes: > Thanks, Samuel. I did read up on inline tasks, while they have the begin/end > structure, they're not really part of the structure of the document. > > Can you point me to the discussion or thread title about this feature - did a > few > searches first but couldn't find anything that looked like what I was talking > about, probably because I'm not describing it in the right terms. I just added an FAQ about this. It contains several links to discussions about closing sections: http://orgmode.org/worg/org-faq.html#closing-outline-sections HTH, Matt
Re: [O] insert picture feature request.
On Mon, May 02, 2011 at 02:42:41PM +0200, Piter_ wrote: > Hi all. > I use org-mode for making note while reading articles. > Sometimes I want to insert picture into notes. Now it takes to much > time. I have to copy paste it into picture editor, save it and than > make a link to it. > I would like to do it in other way. Copy picture into clipboard (from > pdf reader for example), and than run a function in emacs which will > ask for file name, save the picture from clipboard into preset folder > and insert link into org file for it. > I have found those links. > http://stackoverflow.com/questions/1868734/how-to-copy-to-clipboard-with-x11 > http://stackoverflow.com/questions/3571179/how-does-x11-clipboard-handle-multiple-data-formats > > About handling clipboard images from python. > I think it is possible to write a simple python script which can save > clipboard picture into file, and than some lisp function which do all > I described above using this script. > Unfortunately I dont know python and lisp on level which allow me to > do it fast end easy. So I ask if someone can do it. I think it would > be useful addition for org-mode. May be even someone have implemented > it, or made another work arround this problem. > Thanks. > Petro. > P.S. Sorry if you get two copies of request. I had some troubles with > sending it and may sent two versions of this mail. > There was a discussion with a working solution not long ago for taking screenshots and inserting them into org automatically. http://comments.gmane.org/gmane.emacs.orgmode/33770 I suspect the code is on worg. Enjoy. -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
[O] insert picture feature request.
Hi all. I use org-mode for making note while reading articles. Sometimes I want to insert picture into notes. Now it takes to much time. I have to copy paste it into picture editor, save it and than make a link to it. I would like to do it in other way. Copy picture into clipboard (from pdf reader for example), and than run a function in emacs which will ask for file name, save the picture from clipboard into preset folder and insert link into org file for it. I have found those links. http://stackoverflow.com/questions/1868734/how-to-copy-to-clipboard-with-x11 http://stackoverflow.com/questions/3571179/how-does-x11-clipboard-handle-multiple-data-formats About handling clipboard images from python. I think it is possible to write a simple python script which can save clipboard picture into file, and than some lisp function which do all I described above using this script. Unfortunately I dont know python and lisp on level which allow me to do it fast end easy. So I ask if someone can do it. I think it would be useful addition for org-mode. May be even someone have implemented it, or made another work arround this problem. Thanks. Petro. P.S. Sorry if you get two copies of request. I had some troubles with sending it and may sent two versions of this mail.
Re: [O] Implemented word count for subtrees
El Thu, 28 Apr 2011 09:53:17 +0200 Sébastien Vauban va escriure: > > Another suggestion: a variable to choose between a word-count and a > line-count? > Or page-count. With a rough estimator that can predict how many pages each section would take. (Maybe even invoking LaTeX?) This feature is the one I most missed when I had to write a thesis where each section had to have a known number of pages (e.g. introduction 1 page, chapter 1 10 pages, … total 60 pages). I see it as useful enough to go in /contrib/ Many thanks!
Re: [O] revert all org buffers which changed on disk
El Thu, 28 Apr 2011 18:01:04 -0500 Jason Dunsmore va escriure: > > org-revert-all-org-buffers loads all buffers from disk even if they > > didn't change. > > FYI, there's also a package called revbufs: > http://www.neilvandyke.org/revbufs/revbufs.el > That's very useful, thanks. I think org-revert-all-org-buffers does unneeded work and can be optimized, therefore I propose substituting it for org-revert-changed-or-buffers or some code from revbufs.el
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
On May 2, 2011, at 11:52 AM, Antoine Levitt wrote: > 02/05/11 11:20, Carsten Dominik >> Hi Antoine, > > Hi, thanks for replying to this old thread. > >> the agenda does list scheduled items anyway, so I do not see why >> this information should be repeated in the logging items. > > It doesn't list DONE scheduled items. The point is I'd like for log-mode > to be just like the normal agenda, except that it also lists DONE items. > > I think maybe log should just force org-agenda-skip-scheduled-if-done > to t. I don't really think so. A Scheduling timestamp, or a Deadline are for planning. The log view is for displaying when things where actually done. AA work-around for you is to make a custom agenda view and set org-agenda-skip-scheduled-if-done in the options section of that custom command - Carsten > That'd make sense, wouldn't it? Or maybe I'm just extrapolating my > own use case too much, I don't know enough about org usage patterns to > be sure. But I do know that I'd like a function to review my past > appointments/timed todos.
Re: [O] lisp/org-clock.el: Add param :properties to list properties in clocktable
Dear Niels,
I am confused by the three patch pieces applied to the same file.
Can you please resubmit, with a single patch, and a proper
changelog-like entry?
Thanks.
- Carsten
On Mar 26, 2011, at 9:29 PM, Niels Giesen wrote:
>
> Here are a few patches to add property columns in clocktables. These
> allow me e.g. to freely set different cost centers which is wanted @
> my work, and also possibly small descriptions. It is generically set
> up so I reckon other people may find use in this too.
>
> The patches together add two parameters to the dynamic block line:
>
> : :properties ("prop-this" "prop-other") :inherit-props t
>
> The property columns will be added at the left side of the existing
> columns; I did experiment with adding them to the right, but because
> of the variable number of levels (being defined both by :maxlevel and
> the actual number of found levels), that did not work out well.
>
> I used the parameter =:inherit-props= to set inheritance for
> properties, as I have learned in the past that
> =org-use-property-inheritance= should be used very sparingly.
>
> #+begin_src diff
> From 20346cf661e2b9ba0b4a66b705809e6100d9e8e0 Mon Sep 17 00:00:00 2001
> From: Niels Giesen
> Date: Sat, 26 Mar 2011 10:19:08 +0100
> Subject: [PATCH 1/3] org-clock: Add properties param handling to
> `org-clock-get-table-data'
>
> This param should be a list of strings referring to properties. Those
> properties will be returned in an alist when found in an entry.
> ---
> lisp/org-clock.el | 14 +++---
> 1 files changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/lisp/org-clock.el b/lisp/org-clock.el
> index c567a26..df096d1 100644
> --- a/lisp/org-clock.el
> +++ b/lisp/org-clock.el
> @@ -1,6 +1,6 @@
> ;;; org-clock.el --- The time clocking code for Org-mode
>
> -;; Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010
> +;; Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011
> ;; Free Software Foundation, Inc.
>
> ;; Author: Carsten Dominik
> @@ -2335,6 +2335,7 @@ TIME: The sum of all time spend in this tree, in
> minutes. This time
>(block (plist-get params :block))
>(link (plist-get params :link))
>(tags (plist-get params :tags))
> + (properties (plist-get params :properties))
>(matcher (if tags (cdr (org-make-tags-matcher tags
>cc range-text st p time level hdl props tsp tbl)
>
> @@ -2388,8 +2389,15 @@ TIME: The sum of all time spend in this tree, in
> minutes. This time
> (or (cdr (assoc "SCHEDULED" props))
> (cdr (assoc "DEADLINE" props))
> (cdr (assoc "TIMESTAMP" props))
> - (cdr (assoc "TIMESTAMP_IA" props)
> - (when (> time 0) (push (list level hdl tsp time) tbl))
> + (cdr (assoc "TIMESTAMP_IA" props
> + props (when properties
> + (remove nil
> + (mapcar
> + (lambda (p)
> +(when (org-entry-get (point) p)
> + (cons p (org-entry-get (point) p
> + properties
> + (when (> time 0) (push (list level hdl tsp time props) tbl))
> (setq tbl (nreverse tbl))
> (list file org-clock-file-total-minutes tbl
>
> --
> 1.7.1
> #+end_src
>
> #+begin_src diff
> From a5da80e0b42256e1a1ea07e213bcae3685786589 Mon Sep 17 00:00:00 2001
> From: Niels Giesen
> Date: Sat, 26 Mar 2011 11:05:33 +0100
> Subject: [PATCH 2/3] org-clock: Add properties param handling to
> `org-clocktable-write-default'
>
> Each property specified in properties will get a column in the clocktable.
> ---
> lisp/org-clock.el | 10 ++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/lisp/org-clock.el b/lisp/org-clock.el
> index df096d1..a330db0 100644
> --- a/lisp/org-clock.el
> +++ b/lisp/org-clock.el
> @@ -2052,6 +2052,7 @@ from the dynamic block defintion."
>(emph (plist-get params :emphasize))
>(level-p (plist-get params :level))
>(timestamp (plist-get params :timestamp))
> + (properties (plist-get params :properties))
>(ntcol (max 1 (or (plist-get params :tcolumns) 100)))
>(rm-file-column (plist-get params :one-file-with-archives))
>(indent (plist-get params :indent))
> @@ -2115,6 +2116,7 @@ from the dynamic block defintion."
>(if multifile "|" "") ; file column, maybe
>(if level-p "|" "") ; level column, maybe
>(if timestamp "|" "") ; timestamp column, maybe
> + (if properties (make-string (length properties) ?|) "") ;properties
> columns, maybe
>(format "<%d>| |\n" narrow))) ; headline and time columns
>
> ;; Insert the table header line
> @@ -2123,6 +2125,7 @@ from the dynamic block defintion."
>(if multifile (concat (nth 1 lwords) "|
Re: [O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
Hi Antoine,
the agenda does list scheduled items anyway, so I do not see why
this information should be repeated in the logging items.
- Carsten
On Apr 5, 2011, at 12:30 PM, Antoine Levitt wrote:
> I guess my use case is pretty common: I use org-agenda to keep track of
> appointments, and use org-agenda-skip-scheduled-if-done to avoid
> displaying past appointments. If I want to review what I did last week
> for instance, I'd like the SCHEDULED dates to appear in
> org-agenda-log-mode, not the dates where I closed the TODO entry. But
> org-agenda-log-mode-items only has support for closed, clock and state
> changes. A nice feature would be a 'scheduled option, which would
> display done entries that have a SCHEDULED tag.
>
> I tried to implement it, but got stuck at date handling (apparently, the
> problem is that SCHEDULED items use <> syntax, while CLOSED uses
> []. Not sure why.) Could someone take a look at it?
>
> I'm attaching a very preliminary attempt to implement it, in case anyone
> is interested. It's buggy because of the date issues.
>
> diff --git a/lisp/org/org-agenda.el b/lisp/org/org-agenda.el
> index 9adc180..89c9dde 100644
> --- a/lisp/org/org-agenda.el
> +++ b/lisp/org/org-agenda.el
> @@ -4733,6 +4733,7 @@ be skipped."
> (list
>(if (memq 'closed items) (concat "\\<" org-closed-string))
>(if (memq 'clock items) (concat "\\<" org-clock-string))
> + (if (memq 'scheduled items) (concat "\\<"
> org-scheduled-string))
>(if (memq 'state items) "- State \"\\([a-zA-Z0-9]+\\)\".*?"
>(parts-re (if parts (mapconcat 'identity parts "\\|")
>(error "`org-agenda-log-mode-items' is empty")))
> @@ -4744,10 +4745,10 @@ be skipped."
> (format-time-string
>(car org-time-stamp-formats)
>(apply 'encode-time ; DATE bound by calendar
> - (list 0 0 0 (nth 1 date) (car date) (nth 2 date
> + (list 0 0 0 (nth 1 date) (car date) (nth 2 date
> 1 11
>(org-agenda-search-headline-for-time nil)
> - marker hdmarker priority category tags closedp statep clockp state
> + marker hdmarker priority category tags closedp statep clockp
> scheduledp state
>ee txt extra timestr rest clocked)
> (goto-char (point-min))
> (while (re-search-forward regexp nil t)
> @@ -4755,8 +4756,9 @@ be skipped."
> (org-agenda-skip)
> (setq marker (org-agenda-new-marker (match-beginning 0))
> closedp (equal (match-string 1) org-closed-string)
> + scheduledp (equal (match-string 1) org-scheduled-string)
> statep (equal (string-to-char (match-string 1)) ?-)
> - clockp (not (or closedp statep))
> + clockp (not (or closedp scheduledp statep))
> state (and statep (match-string 2))
> category (org-get-category (match-beginning 0))
> timestr (buffer-substring (match-beginning 0) (point-at-eol))
> @@ -4765,7 +4767,7 @@ be skipped."
> ;; substring should only run to end of time stamp
> (setq rest (substring timestr (match-end 0))
> timestr (substring timestr 0 (match-end 0)))
> - (if (and (not closedp) (not statep)
> + (if (and (not closedp) (not statep) (not scheduledp)
> (string-match
> "\\([0-9]\\{1,2\\}:[0-9]\\{2\\}\\)\\].*?\\([0-9]\\{1,2\\}:[0-9]\\{2\\}\\)"
> rest))
> (progn (setq timestr (concat (substring timestr 0 -1)
> "-" (match-string 1 rest) "]"))
> @@ -4780,6 +4782,9 @@ be skipped."
>(setq extra (match-string 1
> (clockp
> (and (looking-at ".*\n[ \t]*-[ \t]+\\([^-\n \t].*?\\)[ \t]*$")
> + (setq extra (match-string 1
> +(scheduledp
> + (and (looking-at ".*\n[ \t]*-[ \t]+\\([^-\n \t].*?\\)[ \t]*$")
>(setq extra (match-string 1)
> (if (not (re-search-backward "^\\*+ " nil t))
> (setq txt org-agenda-no-heading-message)
> @@ -4788,6 +4793,8 @@ be skipped."
> tags (org-get-tags-at))
> (looking-at "\\*+[ \t]+\\([^\r\n]+\\)")
> (setq txt (match-string 1))
> + (if (and scheduledp (not (string-match (regexp-opt
> org-done-keywords-for-agenda) txt)))
> + (throw :skip nil))
> (when extra
> (if (string-match "\\([ \t]+\\)\\(:[^ \n\t]*?:\\)[ \t]*$" txt)
> (setq txt (concat (substring txt 0 (match-beginning 1))
> @@ -4796,8 +4803,9 @@ be skipped."
> (setq txt (org-format-agenda-item
> (cond
> (closedp "Closed:")
> - (statep (concat "State: (" state ")"))
> - (t (concat "Clocked: (" clocked ")")))
> + (scheduledp "Scheduled:")
> +
[O] [Accepted] Add a cross-reference from "Literal Examples" to "Easy Templates."
Patch 755 (http://patchwork.newartisans.com/patch/755/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C1303249505-14163-2-git-send-email-rpgoldman%40sift.info%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] Add a cross-reference from "Literal Examples" to "Easy
> Templates."
> Date: Wed, 20 Apr 2011 02:45:05 -
> From: Robert Goldman
> X-Patchwork-Id: 755
> Message-Id: <1303249505-14163-2-git-send-email-rpgold...@sift.info>
> To: emacs-orgmode@gnu.org
> Cc: "Robert P. Goldman"
>
> From: Robert P. Goldman
>
> Easy templates are especially useful for entering the begin and end pairs
> that arise in supplying literal examples.
>
> ---
> doc/org.texi |4
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/doc/org.texi b/doc/org.texi
> index 8ca4426..17922d4 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -8916,6 +8916,10 @@ If the syntax for the label format conflicts with the
> language syntax, use a
> HTML export also allows examples to be published as text areas, @xref{Text
> areas in HTML export}.
>
> +Because the @code{#+BEGIN_...} and @code{#+END_...} patterns need to be added
> +so often, shortcuts are provided using the Easy Templates facility
> +(@pxref{Easy Templates}).
> +
> @table @kbd
> @kindex C-c '
> @item C-c '
>
[O] [Accepted] [O,Florian,Friesdorf] Re: Org-mode support
Patch 751 (http://patchwork.newartisans.com/patch/751/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C8739li4r52.fsf%40free.fr%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O,Florian,Friesdorf] Re: Org-mode support > Date: Sat, 16 Apr 2011 12:00:41 - > From: Matthieu Lemerre > X-Patchwork-Id: 751 > Message-Id: <8739li4r52@free.fr> > To: emacs-orgmode@gnu.org > Cc: f...@chaoflow.net > > Hi, > > Florian Friesdorf has suggested this patch to org-notmuch so that it is > enough to require org-notmuch in user init, and it seems a good idea. Is > it possible to include his patch? > > Thanks > Matthieu > > > >From 4128169c3d22527342c90b675e847f4227f3b0c1 Mon Sep 17 00:00:00 2001 > From: Florian Friesdorf > Date: Thu, 14 Apr 2011 14:44:54 +0200 > Subject: [PATCH] org-notmuch: require org for org-add-link-type and others > > --- > contrib/lisp/org-notmuch.el |2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/contrib/lisp/org-notmuch.el b/contrib/lisp/org-notmuch.el > index 9cde34f..9283385 100644 > --- a/contrib/lisp/org-notmuch.el > +++ b/contrib/lisp/org-notmuch.el > @@ -41,6 +41,8 @@ > > ;;; Code: > > +(require 'org) > + > ;; Install the link type > (org-add-link-type "notmuch" 'org-notmuch-open) > (add-hook 'org-store-link-functions 'org-notmuch-store-link) > -- > 1.7.4.4 > >
[O] [Accepted] * org-publish.el (org-publish-find-date): optimization
Patch 753 (http://patchwork.newartisans.com/patch/753/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C1303227689-950-1-git-send-email-manuel.giraud%40univ-nantes.fr%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] * org-publish.el (org-publish-find-date): optimization > Date: Tue, 19 Apr 2011 20:41:29 - > From: Manuel Giraud > X-Patchwork-Id: 753 > Message-Id: <1303227689-950-1-git-send-email-manuel.gir...@univ-nantes.fr> > To: emacs-orgmode@gnu.org > Cc: Manuel Giraud > > Hi, > > elp reports important speed gain with this patch to find an org file date. > > --- > lisp/org-publish.el |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/lisp/org-publish.el b/lisp/org-publish.el > index e944eea..7470ee2 100644 > --- a/lisp/org-publish.el > +++ b/lisp/org-publish.el > @@ -852,7 +852,7 @@ system's modification time. > It returns time in `current-time' format." >(let ((visiting (find-buffer-visiting file))) > (save-excursion > - (switch-to-buffer (or visiting (find-file file))) > + (switch-to-buffer (or visiting (find-file-noselect file nil t))) >(let* ((plist (org-infile-export-plist)) >(date (plist-get plist :date))) > (unless visiting >
[O] [Accepted] org-gnus-follow-link and nnimap-request-scan
Patch 747 (http://patchwork.newartisans.com/patch/747/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C8762qjqqfy.fsf%40member.fsf.org%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] org-gnus-follow-link and nnimap-request-scan > Date: Tue, 12 Apr 2011 23:30:17 - > From: Tassilo Horn > X-Patchwork-Id: 747 > Message-Id: <8762qjqqfy@member.fsf.org> > To: emacs-orgmode@gnu.org > > Eden Cardim writes: > > > Tassilo> No, I just wasn't really sure what that SCAN argument > > Tassilo> means, so I tried to be as safe as possible. If it's > > Tassilo> always safe to provide nil, let's change that. > > > > Well, right now all it does is to check split rules against incoming > > mail. But, if we have a link to a message in org, then that message > > already went through the split process, so re-splitting is > > unnecessary. > > Ok, so here we go: > Bye, > Tassilo > > > >From 89fecc7b938385647618dc28c4df304df872e6eb Mon Sep 17 00:00:00 2001 > From: Tassilo Horn > Date: Tue, 12 Apr 2011 20:27:54 +0200 > Subject: [PATCH] Call gnus-activate-group without SCAN arg. > > * org-gnus.el (org-gnus-follow-link): Don't request scan of > group when following link. > --- > lisp/org-gnus.el |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/lisp/org-gnus.el b/lisp/org-gnus.el > index eba4cb4..a5ece8b 100644 > --- a/lisp/org-gnus.el > +++ b/lisp/org-gnus.el > @@ -249,7 +249,7 @@ If `org-store-link' was called with a prefix arg the > meaning of >(when article > (setq article (org-substring-no-properties article))) >(cond ((and group article) > - (gnus-activate-group group t) > + (gnus-activate-group group) >(condition-case nil >(let* ((method (gnus-find-method-for-group group)) > (backend (car method)) > -- > 1.7.5.rc1 > >
[O] [Accepted] Fixed shell script example in "Emacs Lisp evaluation of variables."
Patch 756 (http://patchwork.newartisans.com/patch/756/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C1303405920-1184-2-git-send-email-rpgoldman%40real-time.com%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] Fixed shell script example in "Emacs Lisp evaluation of > variables." > Date: Thu, 21 Apr 2011 22:12:00 - > From: Robert P. Goldman > X-Patchwork-Id: 756 > Message-Id: <1303405920-1184-2-git-send-email-rpgold...@real-time.com> > To: emacs-orgmode@gnu.org > Cc: "Robert P. Goldman" > > The variable names in the header arguments and in the sh code didn't line > up. Made them agree. > > --- > doc/org.texi |4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/doc/org.texi b/doc/org.texi > index 17922d4..e68ed18 100644 > --- a/doc/org.texi > +++ b/doc/org.texi > @@ -12072,8 +12072,8 @@ org-mode file, while there is no such guarantee for > evaluation of the code > block body. > > @example > -#+begin_src sh :var file-name=(buffer-file-name) :exports both > - wc -w $file > +#+begin_src sh :var filename=(buffer-file-name) :exports both > + wc -w $filename > #+end_src > @end example > >
[O] [Accepted] [Orgmode] Removed unecessary invocations of org-agenda-show.
Patch 271 (http://patchwork.newartisans.com/patch/271/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C87zkvly3m3.fsf%40archdesk.localdomain%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [Orgmode] Removed unecessary invocations of org-agenda-show. > Date: Mon, 13 Sep 2010 20:48:27 - > From: Matt Lundin > X-Patchwork-Id: 271 > Message-Id: <87zkvly3m3.fsf@archdesk.localdomain> > To: Org Mode > > lisp/org-agenda.el (org-agenda-set-tags): Remove org-agenda-show to prevent > disrupting windows and changing point in original buffer. > (org-agenda-set-property): Same > (org-agenda-set-effort): Same > (org-agenda-toggle-archive-tag): Same > > When setting a tag in the agenda, org-mode displays the corresponding > entry in the original org buffer by calling org-agenda-show. This has > the unwelcome side-effect of disrupting the current window arrangement > and changing the position of the point in the original buffer. This > behavior is inconsistent with the that of org-agenda-todo, which makes > all its changes "silently." > > Here is the offending line (6799) in org-agenda-set-tags: > > --8<---cut here---start->8--- > (org-agenda-show) ;;; FIXME This is a stupid hack and should not be needed > --8<---cut here---end--->8--- > > The same line occurs in org-agenda-set-property, org-agenda-set-effort, > and org-agenda-toggle-archive tag. > > --- > lisp/org-agenda.el |4 > 1 files changed, 0 insertions(+), 4 deletions(-) > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > index 32c65db..784ba6a 100644 > --- a/lisp/org-agenda.el > +++ b/lisp/org-agenda.el > @@ -6796,7 +6796,6 @@ the same tree node, and the headline of the tree node > in the Org-mode file." >(org-agenda-check-no-diary) >(if (and (org-region-active-p) (interactive-p)) >(call-interactively 'org-change-tag-in-region) > -(org-agenda-show) ;;; FIXME This is a stupid hack and should not be > needed > (let* ((hdmarker (or (org-get-at-bol 'org-hd-marker) >(org-agenda-error))) > (buffer (marker-buffer hdmarker)) > @@ -6825,7 +6824,6 @@ the same tree node, and the headline of the tree node > in the Org-mode file." >"Set a property for the current headline." >(interactive) >(org-agenda-check-no-diary) > - (org-agenda-show) ;;; FIXME This is a stupid hack and should not be > needed >(let* ((hdmarker (or (org-get-at-bol 'org-hd-marker) > (org-agenda-error))) >(buffer (marker-buffer hdmarker)) > @@ -6848,7 +6846,6 @@ the same tree node, and the headline of the tree node > in the Org-mode file." >"Set the effort property for the current headline." >(interactive) >(org-agenda-check-no-diary) > - (org-agenda-show) ;;; FIXME This is a stupid hack and should not be > needed >(let* ((hdmarker (or (org-get-at-bol 'org-hd-marker) > (org-agenda-error))) >(buffer (marker-buffer hdmarker)) > @@ -6872,7 +6869,6 @@ the same tree node, and the headline of the tree node > in the Org-mode file." >"Toggle the archive tag for the current entry." >(interactive) >(org-agenda-check-no-diary) > - (org-agenda-show) ;;; FIXME This is a stupid hack and should not be > needed >(let* ((hdmarker (or (org-get-at-bol 'org-hd-marker) > (org-agenda-error))) >(buffer (marker-buffer hdmarker)) >
Re: [O] [patch] make 'org-save-outline-visibility' return a useful value
Hi Paul, I think this patch is buggy, if only because it introduces an extra closing parenthesis. I have applied a different version - please verify that it does behave as intended. - Carsten On Apr 22, 2011, at 5:11 AM, Paul Sexton wrote: > The macro 'org-save-outline-visibility' in org-macs.el seems like > it should return the value of the last statement in its body (like > save-excursion and save-restriction do). Instead it discards this > value and returns nothing useful. > > The macro is only used in 2 places in the org sources, and its > return value is ignored in both. I feel it would be more useful if > it returned the value of the last expression in its body. A patch > to this effect is attached. > > Paul > > > > --- C:/Users/paul/org-macs.el Fri Apr 22 14:57:07 2011 > +++ C:/Users/paul/org-macs-new.el Fri Apr 22 14:56:51 2011 > @@ -325,8 +325,9 @@ > (declare (indent 1)) > `(let ((data (org-outline-overlay-data ,use-markers))) > (unwind-protect > + (prog1 >(progn > -,@body > + ,@body) > (org-set-outline-overlay-data data)) >(when ,use-markers >(mapc (lambda (c) > > > - Carsten
Re: [O] [PATCH] alt for inline thumbnail
On Apr 22, 2011, at 10:43 AM, Manuel Giraud wrote: > > Hi, > > Here's a patch to add the following syntax for image link in html > exports: > > [[file:hires.jpg][file:thumb.jpg::my description]] > > "my description" will be used for the alt attribute of the thumbnail. > > <0002-org-html.el-org-html-handle-links-use-fragment-part-.patch> To me, this looks like the wrong approach. Instead, the ATTR_HTML should be applied properly also in this case. - Carsten
Re: [O] [PATCH] Sitemap sans extension
Hi Manuel, this has been applied, but please provide a separate patch for the manual to document the new property. - Carsten On Apr 29, 2011, at 3:07 PM, Manuel Giraud wrote: > > Hi, > > The following patch adds an option to remove extensions of files linked > from the auto generated sitemap. This is useful if you want to follow > this: http://www.w3.org/Provider/Style/URI > > <0003-org-publish.el-org-publish-org-sitemap-add-a-sitemap.patch> > -- > Manuel Giraud
[O] [Accepted] Sitemap sans extension
Patch 769 (http://patchwork.newartisans.com/patch/769/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C8762pxxl31.fsf%40univ-nantes.fr%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] Sitemap sans extension > Date: Fri, 29 Apr 2011 18:07:14 - > From: Manuel Giraud > X-Patchwork-Id: 769 > Message-Id: <8762pxxl31@univ-nantes.fr> > To: emacs-orgmode > > Hi, > > The following patch adds an option to remove extensions of files linked > from the auto generated sitemap. This is useful if you want to follow > this: http://www.w3.org/Provider/Style/URI > > > >From 32ca3e459e759fbf6312c0154b1f1ba5b2cb7b13 Mon Sep 17 00:00:00 2001 > From: Manuel Giraud > Date: Fri, 29 Apr 2011 14:57:48 +0200 > Subject: [PATCH 3/3] org-publish.el (org-publish-org-sitemap): add a sitemap > option to > remove extension from filename's link > > --- > lisp/org-publish.el |8 > 1 files changed, 8 insertions(+), 0 deletions(-) > > diff --git a/lisp/org-publish.el b/lisp/org-publish.el > index 7470ee2..56cc80a 100644 > --- a/lisp/org-publish.el > +++ b/lisp/org-publish.el > @@ -178,6 +178,11 @@ sitemap of files or summary page for a given project. > `tree' (the directory structure of the source > files is reflected in the sitemap). Defaults to > `tree'. > + :sitemap-sans-extension Remove extension from sitemap's > + filenames. Useful to have cool > + URIs (see > + http://www.w3.org/Provider/Style/URI). > + Defaults to nil. > >If you create a sitemap file, adjust the sorting like this: > > @@ -758,6 +763,7 @@ Default for SITEMAP-FILENAME is 'sitemap.org'." > (concat "Sitemap for project " (car project >(sitemap-style (or (plist-get project-plist :sitemap-style) > 'tree)) > + (sitemap-sans-extension (plist-get project-plist > :sitemap-sans-extension)) >(visiting (find-buffer-visiting sitemap-filename)) >(ifn (file-name-nondirectory sitemap-filename)) >file sitemap-buffer) > @@ -769,6 +775,8 @@ Default for SITEMAP-FILENAME is 'sitemap.org'." > (let ((fn (file-name-nondirectory file)) > (link (file-relative-name file dir)) > (oldlocal localdir)) > + (when sitemap-sans-extension > + (setq link (file-name-sans-extension link))) > ;; sitemap shouldn't list itself > (unless (equal (file-truename sitemap-filename) >(file-truename file)) > -- > 1.7.3.5 > >
Re: [O] headings with begin/end markers
Samuel Wales gmail.com> writes: > > Hi bertie, > > I don't know, but we've discussed this recently. > > Perhaps it will be possible at some point to insert an inline task and > have it behave as you desire. > > Samuel > Thanks, Samuel. I did read up on inline tasks, while they have the begin/end structure, they're not really part of the structure of the document. Can you point me to the discussion or thread title about this feature - did a few searches first but couldn't find anything that looked like what I was talking about, probably because I'm not describing it in the right terms. Thanks, -bertie
[O] [Accepted] org-get-tags-at: exclude filetags when local is t
Patch 774 (http://patchwork.newartisans.com/patch/774/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C87zkn792zq.fsf%40fastmail.fm%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] org-get-tags-at: exclude filetags when local is t > Date: Sat, 30 Apr 2011 20:19:54 - > From: Matt Lundin > X-Patchwork-Id: 774 > Message-Id: <87zkn792zq@fastmail.fm> > To: Org Mode > > * lisp/org.el (org-get-tags-at): Don't include filetags if local is t. > > The function org-get-tags-at and the functions that called it were > including inherited file tags even if the user requested only local > tags. This patch fixes the behavior. > > --- > lisp/org.el |4 +++- > 1 files changed, 3 insertions(+), 1 deletions(-) > > diff --git a/lisp/org.el b/lisp/org.el > index 61668ce..afcd4cb 100644 > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -12798,7 +12798,9 @@ ignore inherited ones." > (or (org-up-heading-safe) (error nil)) > (setq parent t))) > (error nil) > - (append (org-remove-uniherited-tags org-file-tags) tags) > + (if local > + tags > + (append (org-remove-uniherited-tags org-file-tags) tags)) > > (defun org-add-prop-inherited (s) >(add-text-properties 0 (length s) '(inherited t) s) >
Re: [O] [PATCH] documentation for clocktable :tags syntax
Applied, thanks.
-Carsten
On May 2, 2011, at 8:58 AM, Antti Kaihola wrote:
> After some trial and error I had to dig the mailing lists to figure
> out the syntax of the :tags clock table option. I propose an addition
> to the documentation along these lines:
>
> diff --git a/doc/org.texi b/doc/org.texi
> index 7142ce0..bec1123 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -5892,7 +5892,8 @@ be selected:
> @r{To use this, @code{:block} or @code{:tstart},
> @code{:tend} are needed.}
> :stepskip0 @r{Do not show steps that have zero time.}
> :fileskip0 @r{Do not show table sections from files which did not
> contribute.}
> -:tags@r{A tags match to select entries that should contribute}.
> +:tags@r{A tags match to select entries that should contribute.}
> + @r{See @ref{Matching tags and properties} for the match syntax.}
> @end example
>
> Then there are options which determine the formatting of the table. There
>
- Carsten
