[O] Inline Images Showing as Link
Hi. . . I'm having trouble getting an image URL to render as an inline image in the html export. It always renders it as a link. I have an image saved on Google but Google doesn't preserve the extension which I think confuses org-mode since it doesn't look like an image. Here's the markup: * See the image below: [[https://docs.google .com/leaf?id=0B-swGEqSDpxyMjgwNjE0MzEtMTA4OC00NTdmLWE3MjktMDJmOGE5ZWM2YjY0&hl=en ]] * See the image above I've tried adding a caption thinking that would provide a hint to render as an image but no success there. Can someone advise if there an option I'm missing? Thanks! Andy
Re: [O] Turning on repeat logging for a subtree only
Tom writes: > I generally have repeat logging off, but I want to turn it on > for a certain subtree. > > I added the property LOGGING with the value logrepeat: > > :PROPERTIES: > :LOGGING: logrepeat > :END: > > But this doesn't seem to work, when I toogle the task state > the repeat is not logged. > Works fine for me here. I set org-log-repeat to nil and used the following headline: --8<---cut here---start->8--- * TODO A test :hack: SCHEDULED: <2011-04-20 Wed +1d> :PROPERTIES: :LOGGING: logrepeat :END: --8<---cut here---end--->8--- When I mark it DONE, I get the following results: --8<---cut here---start->8--- * TODO A test :hack: SCHEDULED: <2011-04-21 Thu +1d> :LOGBOOK: - State "DONE" from "TODO" [2011-04-20 Wed 18:32] :END: :PROPERTIES: :LOGGING: logrepeat :LAST_REPEAT: [2011-04-20 Wed 18:32] :END: --8<---cut here---end--->8--- > I checked the source and apparently it is because logrepeat > sets org-log-repeat to 'state, but I want to it to be set to 'time. > > Is there a way to set to it 'time instead of 'state? > AFAICT 'time and 'state are the same thing. Best, Matt
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Matt Lundin writes: > Hi Eric, > > "Eric Schulte" writes: > >> In an attempt to organize my reading notes, I've written the following >> tool which allows both for exporting Org-mode headlines with bibtex >> meta-data to bibtex entries, and for reading existing bibtex entries >> into Org-mode headings. >> >> One nice feature of these functions is the ability to check that all >> required fields are present in a given headline based on the bibtex type >> (e.g., :article, :inproceedings), and prompt for missing fields. >> >> See the top of the elisp file for more usage information. >> https://github.com/eschulte/org-bibtex/blob/master/org-bibtex.el > > Thanks for announcing this! One note: I believe the name conflicts with > a core org-module (org-bibtex.el), which is used to store and open > bibtex links. > Yes, if this is ever included in the contrib directory of Org, the name will have to be changed, although currently I can't think of a good option. Cheers -- Eric > > Best, > Matt > > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Christian Moe writes: > Cool! Thanks for this. I understand the Fireforg project provides part > of this functionality (integrated with Zotero), but this free-standing > tool looks helpful. Three quick comments: > > - I tried to just put this on my load path and require it, but there > seems to be a name conflict with the existing org-bibtex.el, which > provides for BibTeX links. > Oh, good point, I suppose if this is ever winds up in the contrib directory of Org-mode it will need a name change (although no alternate options immediately jump to mind). In the interim I guess you are best off explicitly loading the file with `load'. > > - Trying to create a book type entry, I get prompted only for > :editor', not for `:author'. > Thanks, this is now fixed. > > - Fireforg namespaces the property names with a `BIB_', > e.g. `:BIB_author:', and some people might find that useful as an > option. > I just added a new variable `org-bibtex-prefix' which could be set to e.g., "BIB_" to use such a name prefix. > > - I'd find it helpful with a user option for org-bibtex-fleshout to > prompt for optional fields as well. > Agreed, when `org-bibtex-check' or `org-bibtex-check-all' are called with a prefix argument, they will call `org-bibtex-fleshout' with an optional argument which will result in the inclusion of optional fields. Best -- Eric > > Yours, > Christian > > > On 4/20/11 1:52 AM, Eric Schulte wrote: >> Hi, >> >> In an attempt to organize my reading notes, I've written the following >> tool which allows both for exporting Org-mode headlines with bibtex >> meta-data to bibtex entries, and for reading existing bibtex entries >> into Org-mode headings. >> >> One nice feature of these functions is the ability to check that all >> required fields are present in a given headline based on the bibtex type >> (e.g., :article, :inproceedings), and prompt for missing fields. >> >> See the top of the elisp file for more usage information. >> https://github.com/eschulte/org-bibtex/blob/master/org-bibtex.el >> >> Cheers -- Eric >> > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Matt Lundin writes:
> "Thomas S. Dye" writes:
>
>> This could be very useful and a significant enhancement to Org-mode
>> for note taking. With it, library time can be spent almost entirely
>> within Org-mode, capturing bibliographic information and taking
>> reading notes. It feels like the right level of functionality--
>> lightweight and easy to use, with lots of prompting material.
>>
>> I created an entry with org-bibtex-create and then another with org-
>> bibtex-read/write. When I ran org-bibtex, only the second entry was
>> exported. Also, the org-bibtex-read/write process mangled the bibtex
>> entry a bit, so the resulting .bib file wasn't useful. Note the
>> addition of {} around the publisher and year, and the truncation of
>> multi-line entries.
>
> Just as with auto-generated keys, I wonder whether some of these
> problems might be remedied by plugging into existing bibtex-mode
> functions, especially bibtex-parse-entry and the bibtex string cleanup
> functions. I am always amazed by the ability of bibtex-mode to do the
> right thing when cleaning up entries (e.g., remove delimiters from
> dates, string abbreviations, etc.).
>
Ah, this is a great suggestions and I wish I had thought to look for
existing support before rolling my own versions of these functions.
org-bibtex is now using both of the functions you mentioned above to
good effect.
>
> Also, it might be nice to allow a way to one's existing bibtex entry
> type and field definitions---i.e., bibtex-entry-field-alist.
>
It shouldn't be difficult to add items to the two defvars used by
org-bibtex to manage bibtex entries, namely bibtex-types and
bibtex-fields
Best -- Eric
>
> Best,
> Mat
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Hi Tom,
"Thomas S. Dye" writes:
> Hi Eric,
>
> This could be very useful and a significant enhancement to Org-mode
> for note taking. With it, library time can be spent almost entirely
> within Org-mode, capturing bibliographic information and taking
> reading notes. It feels like the right level of functionality--
> lightweight and easy to use, with lots of prompting material.
>
Thanks, I hope so.
>
> I created an entry with org-bibtex-create and then another with org-
> bibtex-read/write. When I ran org-bibtex, only the second entry was
> exported. Also, the org-bibtex-read/write process mangled the bibtex
> entry a bit, so the resulting .bib file wasn't useful. Note the
> addition of {} around the publisher and year, and the truncation of
> multi-line entries.
>
I /believe/ I have fixed this issue. I am now using pre-existing bibtex
functions for reading in entries, and for cleaning up entries written by
org-bibtex.
>
> Can I suggest some changes?
>
> 1) In our multi-user environment, where several authors are
> contributing to a master bibtex file, we depend on the key generating
> algorithm of bibtex-mode to help weed out duplicate entries. This
> isn't 100% effective, but it catches lots of duplicates and saves us
> time. Would it be possible to lift this mechanism and use it in org-
> bibtex to generate the CUSTOM_ID?
>
I've added a new variable `org-bibtex-autogen-keys' which when set to t
will result in auto-generated keys being used instead of prompting the
user to input such keys.
>
> 2) It might be better to use the (generated) key as the Org headline,
> instead of the title. Titles can be longer than I find comfortable
> for an Org-mode headline, whereas keys are usually about the right
> length.
>
Hmm, I would tend to disagree here, but I think it may be a matter of
taste. Note that if you include a TITLE property in a headline then it
will be used instead of the contents of the headline, leaving you free
to put whatever information you want into the headline. I've just
updated the headline creation so that it will create such a title
property as well as using the title as the headline, leaving you free to
subsequently change the headline.
>
> 3) org-bibtex-cite seems like a natural next step, especially if it
> offers a list of keys in the Org-mode buffer.
>
Meaning a function to allow tab-completion on keys... I could see this
being useful but I would imagine that the bib entries would generally
not live in the same buffer as the Org-mode text... rather I'd think
some sort of global registry would be preferable.
Thanks for the suggestions, bug reports, and examples!
Please do let me know if any of these issues remain -- Eric
>
> Here are the details of my test run:
>
> Existing bibtex entry:
>
> @Book{tuggle94:_cultur_resour_naval_air_station_barber_point,
> author ={H. David Tuggle and M. J. Tomonari-Tuggle and
> D. Colt Denfeld},
> title ={Cultural Resources of Naval Air Station, Barbers
> Point: Summary, Assessment, and Inventory Research
> Design: Task 1b: Archaeological Research Services
> for the Proposed Cleanup, Disposal, and Reuse of
> Naval Air Station, Barbers Point, O`ahu, Hawai`i},
> publisher =iarii,
> year = 1994,
> series ={Prepared for Belt Collins Hawaii},
> address = {Honolulu},
> month = {December}}
>
> Org-mode tree:
>
>
> * Schulte bibtex
>
> ** A journal title
>:PROPERTIES:
>:type: article
>:AUTHOR: A. N. Author
>:JOURNAL: Journal of Statistical Software
>:YEAR: 1998
>:CUSTOM_ID: author_10:article
>:END:
>
> ** {Cultural Resources of Naval Air Station, Barbers
>:PROPERTIES:
>:TYPE: book
>:CUSTOM_ID: tuggle94:_cultur_resour_naval_air_station_barber_point
>:MONTH:December}
>:ADDRESS: Honolulu
>:SERIES: Prepared for Belt Collins Hawaii
>:YEAR: 1994
>:PUBLISHER: iarii
>:AUTHOR: {H. David Tuggle and M. J. Tomonari-Tuggle and
>:END:
>
> Org-bibtex output:
>
> @book{tuggle94:_cultur_resour_naval_air_station_barber_point,
> author={{H. David Tuggle and M. J. Tomonari-Tuggle and},
> title={{Cultural Resources of Naval Air Station, Barbers},
> publisher={iarii},
> year={1994},
> series={Prepared for Belt Collins Hawaii},
> address={Honolulu},
> month={December}}
> }
>
> hth,
> Tom
>
> On Apr 19, 2011, at 1:52 PM, Eric Schulte wrote:
>
>> Hi,
>>
>> In an attempt to organize my reading notes, I've written the following
>> tool which allows both for exporting Org-mode headlines with bibtex
>> meta-data to bibtex entries, and for reading existing bibtex entries
>> into Org-mode headings.
>>
>> One nice feature of these functions is the ability to check that all
>> required fields are present in a given headline based on the bibtex
>> type
>> (e.g., :article, :inproceedings), and prompt for missing fields.
>>
>
Re: [O] create new files from capture
Bill Wishon wrote: > Bill Wishon wishon.org> writes: > > > What I'm trying to figure out now is how to read the template from a file. > > The documentation says that it can be done by using (file "path/to/file") > > in place of the template text argument, but I haven't gotten that working > > yet. > > Nevermind, my elisp skills are rusty (file "path/to/template.org") works fine, > what I was trying to do required lisp code evaluation in that context and > therefore didn't work eg: (file (concat org-directory "/template.org")) to do > that I'd have to use (function function-returning-the-template), but it's not > really worth it for what I was trying to do. > Alternatively, you can use the backquote mechanism - see e.g. http://thread.gmane.org/gmane.emacs.orgmode/17612/focus=17620 Nick
Re: [O] NEW auto dimension tables doesn't work in orgtbl Text mode
On Thu, Apr 21, 2011 at 00:53, Sebastian Szwarc wrote: > Ok here it is: > Aquamacs version: newest :) > Snow Leopard 10.6.7 > > Set - unicode UTF-8 > Font for text mode - Lucida Grande 13pt > > And this is how it looks > > http://img861.imageshack.us/i/zrzutekranu20110420godz.png/ Samuel Wales was on the money: Lucida Grande is a variable-width font. Org-mode expects fixed-width (monospaced) fonts, i.e. fonts where every character has the same width, such as Courier or Consolas. With a fixed-width font, tables can be aligned by simply making sure each cell contains the same number of characters through padding smaller values with spaces and truncating larger values. With a variable-width font, on the other hand, it’s much more complicated (if it’s possible at all—I think you’d have to do weird things with images). Try a different font, e.g. Lucida Console, and you will see things lining up correctly. Aankhen
Re: [O] NEW auto dimension tables doesn't work in orgtbl Text mode
Ok here it is: Aquamacs version: newest :) Snow Leopard 10.6.7 Set - unicode UTF-8 Font for text mode - Lucida Grande 13pt And this is how it looks http://img861.imageshack.us/i/zrzutekranu20110420godz.png/ regards Sebastian
Re: [O] create new files from capture
Bill Wishon wishon.org> writes: > What I'm trying to figure out now is how to read the template from a file. > The documentation says that it can be done by using (file "path/to/file") > in place of the template text argument, but I haven't gotten that working yet. Nevermind, my elisp skills are rusty (file "path/to/template.org") works fine, what I was trying to do required lisp code evaluation in that context and therefore didn't work eg: (file (concat org-directory "/template.org")) to do that I'd have to use (function function-returning-the-template), but it's not really worth it for what I was trying to do. ~>Bill
Re: [O] Feature request: modify italic regexp list to include non-breaking space and other characters
On Wed, Apr 20, 2011 at 20:34, wrote:
> Sample code:
> Using /a/’s and /b/’s, write add /x/ + 2.
> ^ ^ ^ ^
> Right single quotation mark Non-breaking space
>
> Expected HTML export:
> Using a’s and b’s, write x + 2.
>
> Actual HTML export:
> Using /a/’s and /b/’s, write add /x/ + 2.
Interestingly, the development version treats this differently, as it
considers all the text from the first slash to the last part of the
emphasis:
,
| Using a/’s and /b/’s, write add /x + 2.
|
`
(This behaviour occurs in the original Org buffer as well, in case
anyone’s wondering. The exported HTML was just the easiest way to
show it.)
> If it's not clear, the sample code uses the unicode character "right single
> character" instead of an apostrophe and "non-breaking space" instead of
> regular white space.
>
> It makes sense to use these characters this way, however, orgmode neither
> displays the italic expressions correctly nor exports them correctly.
>
> I believe older versions of orgmode worked in the expected way.
>
> How can I modify the regexp list? Bold characters are also affected.
These two variables are used to configure the regexp:
,[ C-h v org-emphasis-alist RET ]
| org-emphasis-alist is a variable defined in `org.el'.
| Its value is (("*" bold "" "")
| ("/" italic "" "")
| ("_" underline "" "")
| ("=" org-code "" "" verbatim)
| ("~" org-verbatim "" "" verbatim)
| ("+"
| (:strike-through t)
| "" ""))
|
|
| Documentation:
| Special syntax for emphasized text.
| Text starting and ending with a special character will be emphasized, for
| example *bold*, _underlined_ and /italic/. This variable sets the marker
| characters, the face to be used by font-lock for highlighting in Org-mode
| Emacs buffers, and the HTML tags to be used for this.
| For LaTeX export, see the variable `org-export-latex-emphasis-alist'.
| For DocBook export, see the variable `org-export-docbook-emphasis-alist'.
| Use customize to modify this, or restart Emacs after changing it.
|
| You can customize this variable.
`
,[ C-h v org-emphasis-regexp-components RET ]
| org-emphasis-regexp-components is a variable defined in `org.el'.
| Its value is (" ('\"{" "- .,:!?;'\")}\\" "
\n,\"'" "." 1)
|
|
| Documentation:
| Components used to build the regular expression for emphasis.
| This is a list with five entries. Terminology: In an emphasis string
| like " *strong word* ", we call the initial space PREMATCH, the final
| space POSTMATCH, the stars MARKERS, "s" and "d" are BORDER characters
| and "trong wor" is the body. The different components in this variable
| specify what is allowed/forbidden in each part:
|
| pre Chars allowed as prematch. Beginning of line will be
allowed too.
| post Chars allowed as postmatch. End of line will be allowed too.
| border The chars *forbidden* as border characters.
| body-regexp A regexp like "." to match a body character. Don't use
| non-shy groups here, and don't allow newline here.
| newline The maximum number of newlines allowed in an emphasis exp.
|
| Use customize to modify this, or restart Emacs after changing it.
|
| You can customize this variable.
|
| [back]
`
I’d say that ‘pre’/‘post’ should really contain [[:space:]], but then
Org’s syntax table seems to treat the non-breaking space as
punctuation, so that wouldn’t help. You could try adding the
character itself to both of those categories for a fix. You’ll need
to restart Emacs afterwards (unless you used the Customize interface)
so that ‘org-emph-re’ is updated accordingly.
> Using 7.4.
This little problem aside, you might want to upgrade (if not to the
development version, at least to 7.5).
Aankhen
Re: [O] create new files from capture
> (function function-finding-location)
> Most general way, write your own function to find both
> file and location
I just started trying to do this today myself when I found this thread.
>From what I can tell the expectation is that this function places the point
in the buffer/file at the location where you want to insert the captured
template item.
I created to following which works for me to open a new file and puts the
test template there:
(defun prompt-for-new-orgfile ()
"This function prompts for a file to save to"
(call-interactively 'find-file)
(end-of-buffer))
(setq org-capture-templates
'(("t" "Todo" entry (file+headline (concat org-directory "/gtd.org")
"Tasks")
"* TODO %?\n %i\n %a")
("m" "Meeting Notes" entry (function prompt-for-new-orgfile)
"* %^{meetingtitle}" :unnarrowed)))
What I'm trying to figure out now is how to read the template from a file.
The documentation says that it can be done by using (file "path/to/file")
in place of the template text argument, but I haven't gotten that working yet.
~>Bill
Re: [O] include an .org file and lower the level of all its headers
This is a feature that I was just looking for, and I'm pretty excited about it. However, I find that providing this new facility leads me to look for another one: relativizing links. It seems like when I include another file, the links in that other file get messed up. In particular, I have figures in the sub-file, and AFAICT it looks like the sub-files file links aren't working correctly. Or maybe that's not what's really wrong: the symptoms I am seeing are missing pdfs + a blizzard of warnings that look like this: No match - create this as a new heading? (y or n) I suspect that this message is intended to be seen at a time when its meaning will be more obvious to the user. Any suggestions? thanks, r
Re: [O] Indentation of org-mode code
Manuel Giraud writes: > Bernt Hansen writes: > >> For indenting lisp code I highlight the region to indent and C-M-\ >> (which is M-x indent-region) > > Yes I know (and do). But if you try this on org-html.el, for example, > big chunks of code are indented differently than they are now. So I > thought that there was some convention for indenting org-mode code. Not that I'm aware of - but you should refrain from making unnecessary whitespace changes to the code base even if the existing code is incorrectly formatted. Reformat the stuff you touch but don't make copious whitespace changes - that just hides what you changed. Regards, Bernt
[O] Case Sensitive Radio Target?
Radio Targets appear to be case insensitive. Is there a way to make them case sensitive? -- dtm
Re: [O] [ANN] neo - No Emacs Org in Python
Olivier Schwander chadok.info> writes: > > Limitations > > - Read-only (no org file modifications support) > - No drawers parsing > - No exporters > - No formaters parsing (like ==, //, ** and so on, it > will wait for exporters) > - No filtering support > Hi Olivier, nice to see a new project about org and python. Maybe you should have a look at my project too: https://github.com/bjonnh/PyOrgMode that supports reading and writing of org-files, drawers,… Don't know if it can be of some help to you (or maybe just inspiring you). Cheers, Jonathan
Re: [O] [ANN] neo - No Emacs Org in Python
El mar, 19 abr 2011, Olivier Schwander decía:
> Dear Org users,
>
> I am pleased to do the first announce of neo, which stands for "No Emacs
> Org". The goal of this project is to provide a full implementation of
> Org usable in Python.
Excelent!! but find some errors:
- Fix setup.py for install:
diff -rN old-neo/setup.py new-neo/setup.py
12c12
< packages = ['org'],
---
> packages = ['org','org.actions'],
- Add README with required packages:
# apt-get install python-argparse python-yaml
# easy install texttable
- Find bug parsing <20> (width column in table) as DATE
- Error in the line type = repeat.group("type")
--
((.)) Osiris Alejandro Gomez (OSiUX) os...@osiux.com.ar
| E1B1 EB8E E37B 10B3 47E9 D73A 2C09 297C FFB9 4410
-)| http://wiki.buenosaireslibre.org/NodoOsiux
|(- 10.4.14.225 osiux.osiux.bal
signature.asc
Description: Digital signature
[O] Feature request: modify italic regexp list to include non-breaking space and other characters
Sample code: Using /a/’s and /b/’s, write add /x/ + 2. ^ ^^ ^ Right single quotation markNon-breaking space Expected HTML export: Using a’s and b’s, write x + 2. Actual HTML export: Using /a/’s and /b/’s, write add /x/ + 2. If it's not clear, the sample code uses the unicode character "right single character" instead of an apostrophe and "non-breaking space" instead of regular white space. It makes sense to use these characters this way, however, orgmode neither displays the italic expressions correctly nor exports them correctly. I believe older versions of orgmode worked in the expected way. How can I modify the regexp list? Bold characters are also affected. Using 7.4.
Re: [O] Indentation of org-mode code
Bernt Hansen writes: > For indenting lisp code I highlight the region to indent and C-M-\ > (which is M-x indent-region) Yes I know (and do). But if you try this on org-html.el, for example, big chunks of code are indented differently than they are now. So I thought that there was some convention for indenting org-mode code. -- Manuel Giraud
Re: [O] Indentation of org-mode code
Manuel Giraud writes: > Hi, > > What are the good settings to indent the org-mode code? I have searched > through the mailing list and worg but can't find an answer. > > I'm asking because while working on org-html.el at one point I reindent > the whole buffer and end up with a mess (indenting with "emacs -Q" can't > fix this). For indenting lisp code I highlight the region to indent and C-M-\ (which is M-x indent-region) -Bernt
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Matt Lundin writes: > Also, it might be nice to allow a way to one's existing bibtex entry ^ use - > type and field definitions---i.e., bibtex-entry-field-alist.
[O] Indentation of org-mode code
Hi, What are the good settings to indent the org-mode code? I have searched through the mailing list and worg but can't find an answer. I'm asking because while working on org-html.el at one point I reindent the whole buffer and end up with a mess (indenting with "emacs -Q" can't fix this). Best, -- Manuel Giraud
Re: [O] Filtering agenda by tags.
Radosław Grzanka writes:
> yes, I've simplified examples to the point which made no sense. I'm
> very sorry.
> All entries should have had some kind of timestamp, deadline or
> schedule. Yes, I'd like daily/weekly agenda view filtered by tags.
No problem. Maybe the tags search examples I provided will prove useful
to someone else who stumbles across them. :)
> - org-agenda-filter-preset - but that seems not to support "or" (maybe
> I'm missing something?)
Filtering allows for inherited tags but not for or logic. It's a quick
and simple way to include or exclude by tag. E.g., '("+work" "+internet")
will filter for items tagged work and internet.
> - org-agenda-skip-function - which I found googling around - with
> regexp like '(org-agenda-skip-subtree-if 'regexp ":work:")' - but that
> seems not to support "inherited" tags.
The regexp argument of org-agenda-skip-subtree-if function, on the other
hand, allows for or logic but not for inherited tags. E.g.,
(org-agenda-skip-subtree-if 'notregexp ":\\(work\\|internet\\):")
...will find items tagged with work or internet, but only if they are
local.
I believe the only option is to write a skip function that uses
org-entry-get to get all the tags at point.
Here's an example:
--8<---cut here---start->8---
(defun org-agenda-skip-entry-unless-tags (tags)
"Skip entries that do not contain specified tags.
TAGS is a list specifying which tags should be displayed.
Inherited tags will be considered."
(let ((subtree-end (save-excursion (org-end-of-subtree t)))
(atags (split-string (org-entry-get nil "ALLTAGS") ":")))
(if (catch 'match
(mapc (lambda (tag)
(when (member tag atags)
(throw 'match t)))
tags)
nil)
nil
subtree-end)))
(setq org-agenda-custom-commands
'(("x" "Work and internet" agenda ""
((org-agenda-skip-function '(org-agenda-skip-entry-unless-tags
'("work" "internet")))
--8<---cut here---end--->8---
Best,
Matt
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
"Thomas S. Dye" writes:
> This could be very useful and a significant enhancement to Org-mode
> for note taking. With it, library time can be spent almost entirely
> within Org-mode, capturing bibliographic information and taking
> reading notes. It feels like the right level of functionality--
> lightweight and easy to use, with lots of prompting material.
>
> I created an entry with org-bibtex-create and then another with org-
> bibtex-read/write. When I ran org-bibtex, only the second entry was
> exported. Also, the org-bibtex-read/write process mangled the bibtex
> entry a bit, so the resulting .bib file wasn't useful. Note the
> addition of {} around the publisher and year, and the truncation of
> multi-line entries.
Just as with auto-generated keys, I wonder whether some of these
problems might be remedied by plugging into existing bibtex-mode
functions, especially bibtex-parse-entry and the bibtex string cleanup
functions. I am always amazed by the ability of bibtex-mode to do the
right thing when cleaning up entries (e.g., remove delimiters from
dates, string abbreviations, etc.).
Also, it might be nice to allow a way to one's existing bibtex entry
type and field definitions---i.e., bibtex-entry-field-alist.
Best,
Mat
Re: [O] Filtering agenda by tags.
W dniu 2011-04-20 15:12, Matt Lundin pisze: Radosław Grzanka writes: Hello, W dniu 2011-04-20 14:52, Matt Lundin pisze: I'd like to have two agenda views: 1. should show things I can do at work and internet and untagged tasks 2. should show things I can do at home and internet and untagged tasks The simplest solution is just to use a query/match (as above). The variables org-agenda-filter-preset and org-agenda-skip-function are meant primarily for agenda views, which are built around timestamps Which is exactly what I want - maybe I was not clear enough. I don't want tags search. I want agenda view without entries with given tags (or entries only with given tags). Could you please clarify what you mean by an agenda view. Do you mean the daily/weekly agenda? None of the examples you provided have timestamps, so they would not show up in the *daily/weekly* agenda view unless you had org-agenda-include-all-todo set to t. Hi, yes, I've simplified examples to the point which made no sense. I'm very sorry. All entries should have had some kind of timestamp, deadline or schedule. Yes, I'd like daily/weekly agenda view filtered by tags. Thanks for helping, Radek.
Re: [O] Filtering agenda by tags.
Radosław Grzanka writes: > Hello, > > W dniu 2011-04-20 14:52, Matt Lundin pisze: >>> I'd like to have two agenda views: >>> >>> 1. should show things I can do at work and internet and untagged tasks >>> 2. should show things I can do at home and internet and untagged tasks > >> The simplest solution is just to use a query/match (as above). The >> variables org-agenda-filter-preset and org-agenda-skip-function are >> meant primarily for agenda views, which are built around timestamps > > Which is exactly what I want - maybe I was not clear enough. I don't > want tags search. I want agenda view without entries with given tags > (or entries only with given tags). Could you please clarify what you mean by an agenda view. Do you mean the daily/weekly agenda? None of the examples you provided have timestamps, so they would not show up in the *daily/weekly* agenda view unless you had org-agenda-include-all-todo set to t. Best, Matt
Re: [O] Filtering agenda by tags.
Hello, W dniu 2011-04-20 14:52, Matt Lundin pisze: I'd like to have two agenda views: 1. should show things I can do at work and internet and untagged tasks 2. should show things I can do at home and internet and untagged tasks The simplest solution is just to use a query/match (as above). The variables org-agenda-filter-preset and org-agenda-skip-function are meant primarily for agenda views, which are built around timestamps Which is exactly what I want - maybe I was not clear enough. I don't want tags search. I want agenda view without entries with given tags (or entries only with given tags). Thanks, Radek. P.S. After not-so-much thinking "untagged" makes no sense anymore.
Re: [O] Filtering agenda by tags.
Radosław Grzanka writes:
> Hello,
> I have another problem which I fail on resolving.
>
> Let's say I have a org file
>
> --
> #+FILETAGS: work
>
> * Do something at work
> * Do something at the internet:internet:
> --
>
> and another file:
>
> --
>
> * Do something at home:home:
> * Do something at the internet:internet:
> * Some other untagged task
>
> --
>
> I'd like to have two agenda views:
>
> 1. should show things I can do at work and internet and untagged tasks
> 2. should show things I can do at home and internet and untagged tasks
>
(setq org-agenda-custom-commands
'(("x" "Work and internet and untagged" tags "+work|+internet|-TAGS={.}")
("X" "Home and internet and untagged" tags
"+home|+interent|-TAGS={.}")))
I am assuming that when you say "untagged", you mean items without local
tags. If you want inherited tags to be considered, use ALLTAGS instead.
> I fail with defining custom agenda views. I've browsed google and
> already tried:
> - org-agenda-filter-preset - but that seems not to support "or" (maybe
> I'm missing something?)
> - org-agenda-skip-function - which I found googling around - with
> regexp like '(org-agenda-skip-subtree-if 'regexp ":work:")' - but that
> seems not to support "inherited" tags.
The simplest solution is just to use a query/match (as above). The
variables org-agenda-filter-preset and org-agenda-skip-function are
meant primarily for agenda views, which are built around timestamps
rather than tags searches. When simply searching for tags, the tags
matcher is the best bet.
Note, you could accomplish the same thing with:
C-c a m "work|internet|-TAGS={.}"
See the following for more information:
- (info "(org) Tag searches")
- (info "(org) Matching tags and properties")
- http://orgmode.org/worg/org-tutorials/advanced-searching.html#tag-searches
- http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.html
Best,
Matt
Re: [O] Formal description of Org files
Le 15 Apr 2011 14:31, Nick Dokos a écrit: > Eric Schulte wrote: > > > If one goal of such a formal description of Org-mode would be to parse > > text Org-mode files into an abstract syntax tree ... > > > > I think this should be the starting point: what are the goals for all this? > Providing a formal description in EBNF is one thing. Preparing an attribute > grammar for input into a specific tool is another (and probably an order of > magnitude - or two - harder) - what would the resulting parser(s) be used for? > > Clear(er) answers to these questions should go a long way towards figuring out > what specific tool(s) should be used - or whether it's at all necessary to > worry about that. The primary goal I see for such a formal description is to provide a specification that third party parsers are supposed to respect. Writing a real parser may be too much project specific and difficult to generalize in a way usable by the community. During the development of neo[1], I was confronted to the need of defining what is an org file (actually, what is an headline, a todo keyword, a tag, a drawer, a timestamp, etc) and determining what is the expected output of a parser. Maybe the most appropriate format for such a description would be free text, letting parser developers choosing between context-free grammars, regexps or whatever they want ( with a bunch of example org files for reference and tests). Regards, Olivier [1] I am just discovering this thread
[O] Bug in inlinetask export or latex export?
I have a document that looks like the following. If I export the whole file, I get the whole file. (I'm exporting to LaTeX using C-c C-e d.) If I move to the line "** Level 2 A" and export that subtree using C-c C-e 1 d, the inline tasks are omitted. Is this a bug or have I just misconfigured this somehow? It seems to be caused by the fact that those inline tasks are treated as "lines before the first headline" and that org-export-latex-first-lines calls org-export-preprocess-string with a more-or-less hardcoded opt-plist that doesn't include :tasks. Is there a reason not to modify this section of org-export-latex-first-lines: (org-export-latex-content (org-export-preprocess-string (buffer-substring pt end) :for-backend 'latex :emph-multiline t :add-text nil :comments nil :skip-before-1st-heading nil :LaTeX-fragments nil :tasks (plist-get opt-plist :tasks);; <-- this is the line I want to add :timestamps (plist-get opt-plist :timestamps) :footnotes (plist-get opt-plist :footnotes))) -- * Level 1 A ** Level 2 A test *** TODO Test 1 *** END *** TODO Test 2 *** END *** TODO Test 3 *** END test2 and more ** Level 2 B --
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Hi Eric, "Eric Schulte" writes: > In an attempt to organize my reading notes, I've written the following > tool which allows both for exporting Org-mode headlines with bibtex > meta-data to bibtex entries, and for reading existing bibtex entries > into Org-mode headings. > > One nice feature of these functions is the ability to check that all > required fields are present in a given headline based on the bibtex type > (e.g., :article, :inproceedings), and prompt for missing fields. > > See the top of the elisp file for more usage information. > https://github.com/eschulte/org-bibtex/blob/master/org-bibtex.el Thanks for announcing this! One note: I believe the name conflicts with a core org-module (org-bibtex.el), which is used to store and open bibtex links. Best, Matt
Re: [O] Formal description of Org files
If I remember well, the thing with BNF and similar approaches was called 'context free grammar' - and I'm not sure, if this requirement is fullfilled by the org syntax. As I mean to remember is e.g. that Perl could not be declared fully with a context free grammar. As if 'parse an org-file completely into a token stream' is not required by syntax highlighting tools etc, it might be enough to give some regexps or so. Perhaps for use with etags. Perhaps for modifying ecb to extract main elements of an org-file into it's subwindows. Greetings, Olaf
[O] Filtering agenda by tags.
Hello, I have another problem which I fail on resolving. Let's say I have a org file -- #+FILETAGS: work * Do something at work * Do something at the internet:internet: -- and another file: -- * Do something at home:home: * Do something at the internet:internet: * Some other untagged task -- I'd like to have two agenda views: 1. should show things I can do at work and internet and untagged tasks 2. should show things I can do at home and internet and untagged tasks I fail with defining custom agenda views. I've browsed google and already tried: - org-agenda-filter-preset - but that seems not to support "or" (maybe I'm missing something?) - org-agenda-skip-function - which I found googling around - with regexp like '(org-agenda-skip-subtree-if 'regexp ":work:")' - but that seems not to support "inherited" tags. I'm using latest git checkout org and emacs 23.3.1 on windows. Thanks for any tip Radek.
Re: [O] [PATCH] * org-html.el (org-html-handle-links): add an alternate for inline images
Aankhen writes: > On Wed, Apr 20, 2011 at 13:39, Manuel Giraud > wrote: > >> I knew it was not the best solution: all i wanted was to validate. But >> an empty alt or maybe just "image" is fine by me too. > > Fair enough. :-) ‘image’ would be about the same as the file name in > terms of useful alt text. :-) and as useful as "" which is 5 bytes shorter: I think you've won here. > Well, there /is/ a way to do that already, it’s just verbose: > > ,[ Org ] > | * Foo > | #+ATTR_HTML: alt="The elusive foo in its native habitat." > | [[file:foo.png]] > ` Yes, discovered that in the doc just after posting my reply. But, this doesn't work on [[big.jpg][small.jpg]] links as the alt attribute will be placed in the anchor (which is wrong, AFAICT). > I’d suggest using the description part of the link as the alt text, > but then there’d be no way to provide the actual link text (or image, > as the case may be), so that’s a non-starter. Now, I'm looking into using the fragment part: less verbose and hopefully it'll work for all kind of inline image. -- Manuel Giraud
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Cool! Thanks for this. I understand the Fireforg project provides part of this functionality (integrated with Zotero), but this free-standing tool looks helpful. Three quick comments: - I tried to just put this on my load path and require it, but there seems to be a name conflict with the existing org-bibtex.el, which provides for BibTeX links. - Trying to create a book type entry, I get prompted only for `:editor', not for `:author'. - Fireforg namespaces the property names with a `BIB_', e.g. `:BIB_author:', and some people might find that useful as an option. - I'd find it helpful with a user option for org-bibtex-fleshout to prompt for optional fields as well. Yours, Christian On 4/20/11 1:52 AM, Eric Schulte wrote: Hi, In an attempt to organize my reading notes, I've written the following tool which allows both for exporting Org-mode headlines with bibtex meta-data to bibtex entries, and for reading existing bibtex entries into Org-mode headings. One nice feature of these functions is the ability to check that all required fields are present in a given headline based on the bibtex type (e.g., :article, :inproceedings), and prompt for missing fields. See the top of the elisp file for more usage information. https://github.com/eschulte/org-bibtex/blob/master/org-bibtex.el Cheers -- Eric
Re: [O] [PATCH] * org-html.el (org-html-handle-links): add an alternate for inline images
On Wed, Apr 20, 2011 at 13:39, Manuel Giraud wrote: > Aankhen writes: > >> This might not be the best solution. The purpose of the ‘alt’ >> attribute is to provide a textual alternative, which the file name >> really isn’t. It would be better to provide an empty value: >> >> [snip] > > I knew it was not the best solution: all i wanted was to validate. But > an empty alt or maybe just "image" is fine by me too. Fair enough. :-) ‘image’ would be about the same as the file name in terms of useful alt text. >> I took a look at ‘org-html.el’ and changed the relevant line, but it >> doesn’t seem to have any effect. > > I've tested my patch only on [[big_image.png][small_image.png]] kind of > link (maybe that's why). Possibly—while I was hacking on it, I couldn’t quite pin down when it had an effect and when it didn’t. >> [snip] > > Ok, those 2 last hunk should complete my patch I guess. But what I'd > really like is a way to set a alt as a user. Maybe something like this: > > [[big_image.png][small_image.png|my picture is cool]] > > What you guys think? I'll look what i can do and try to make it work for > anykind of tag that can be generated. Well, there /is/ a way to do that already, it’s just verbose: ,[ Org ] | * Foo | #+ATTR_HTML: alt="The elusive foo in its native habitat." | [[file:foo.png]] ` ,[ HTML ] | | 1 Foo | | | | | ` I’d suggest using the description part of the link as the alt text, but then there’d be no way to provide the actual link text (or image, as the case may be), so that’s a non-starter. Aankhen
[O] Turning on repeat logging for a subtree only
I generally have repeat logging off, but I want to turn it on for a certain subtree. I added the property LOGGING with the value logrepeat: :PROPERTIES: :LOGGING: logrepeat :END: But this doesn't seem to work, when I toogle the task state the repeat is not logged. I checked the source and apparently it is because logrepeat sets org-log-repeat to 'state, but I want to it to be set to 'time. Is there a way to set to it 'time instead of 'state? And BTW why this 'state value is not documented in the docstring of org-log-repeat? Isn't it a doc bug? http://repo.or.cz/w/org-mode.git/blob/HEAD:/lisp/org.el#l2435
Re: [O] How can I review a day?
On 19 April 2011 18:12, Bernt Hansen wrote: > > Hi Robert, > > From section 10.5 of the org-mode manual > > --8<---cut here---start->8--- > `v l or short l (`org-agenda-log-mode')' > Toggle Logbook mode. In Logbook mode, entries that were marked > DONE while logging was on (variable `org-log-done') are shown in > the agenda, as are entries that have been clocked on that day. > ^ > You can configure the entry types that should be included in log > mode using the variable `org-agenda-log-mode-items'. When called > with a `C-u' prefix, show all possible logbook entries, including > state changes. When called with two prefix args `C-u C-u', show > only logging information, nothing else. `v L' is equivalent to > `C-u v l'. > --8<---cut here---end--->8--- > > If you have any suggestions on how to improve this please let us know. Well, I would have said "a pointer/cross-reference from the "Clocking work time" section". But actually, I see there *is* a link, at the foot of 8.4.1. But I didn't see it (or its significance did not register). Trying to re-construct my previous mental state, I think I believed that the "Agenda" seemed to be about TODOs and the like, and I'm not currently using that. So I didn't look/see the options that it offers, and nothing cued me to the fact that it could/would display clocked time. SO, two suggestions that would have maybe helped me: The "full monty" solution would be to create a new sub-section on "Correcting clocked time", and actually spell out what you can do to fix up your clocked time when the you realise you've done it wrong. And add a sentence or two at the end of the first para of 8.4, saying that clocked working time can be shown in some Agenda displays, and mentioning the "l" option. ((Good grief! While writing this, I've just tried the command again, and noticed that all previous activity on the current task is highlighted. NEAT! )) Anyway, I'm a happy camper. Thanks for all your help. > > Regards, > Bernt > Robert. -- Robert Inder, 0131 229 1052 / 07808 492 213 Interactive Information Ltd, 3, Lauriston Gardens, Edinburgh EH3 9HH Registered in Scotland, Company no. SC 150689 Interactions speak louder than words
Re: [O] [PATCH] * org-html.el (org-html-handle-links): add an alternate for inline images
Aankhen writes: > This might not be the best solution. The purpose of the ‘alt’ > attribute is to provide a textual alternative, which the file name > really isn’t. It would be better to provide an empty value: > > , > | > ` I knew it was not the best solution: all i wanted was to validate. But an empty alt or maybe just "image" is fine by me too. > I took a look at ‘org-html.el’ and changed the relevant line, but it > doesn’t seem to have any effect. I've tested my patch only on [[big_image.png][small_image.png]] kind of link (maybe that's why). > @@ -1839,8 +1838,8 @@ lang=\"%s\" xml:lang=\"%s\"> >"Create image tag with source and attributes." >(save-match-data > (if (string-match "^ltxpng/" src) > - (format "" > -src (org-find-text-property-in-string 'org-latex-src src)) > + (format "" > +src) >(let* ((caption (org-find-text-property-in-string 'org-caption src)) > (attr (org-find-text-property-in-string 'org-attributes src)) > (label (org-find-text-property-in-string 'org-label src))) > @@ -1855,7 +1854,7 @@ lang=\"%s\" xml:lang=\"%s\"> > src > (if (string-match "\\ (concat " " attr ) > - (concat " " attr " alt=\"" src "\""))) > + (concat " " attr " alt=\"\""))) > (if caption > (format "%s > %s" Ok, those 2 last hunk should complete my patch I guess. But what I'd really like is a way to set a alt as a user. Maybe something like this: [[big_image.png][small_image.png|my picture is cool]] What you guys think? I'll look what i can do and try to make it work for anykind of tag that can be generated. -- Manuel Giraud
Re: [O] [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Hi Eric,
This could be very useful and a significant enhancement to Org-mode
for note taking. With it, library time can be spent almost entirely
within Org-mode, capturing bibliographic information and taking
reading notes. It feels like the right level of functionality--
lightweight and easy to use, with lots of prompting material.
I created an entry with org-bibtex-create and then another with org-
bibtex-read/write. When I ran org-bibtex, only the second entry was
exported. Also, the org-bibtex-read/write process mangled the bibtex
entry a bit, so the resulting .bib file wasn't useful. Note the
addition of {} around the publisher and year, and the truncation of
multi-line entries.
Can I suggest some changes?
1) In our multi-user environment, where several authors are
contributing to a master bibtex file, we depend on the key generating
algorithm of bibtex-mode to help weed out duplicate entries. This
isn't 100% effective, but it catches lots of duplicates and saves us
time. Would it be possible to lift this mechanism and use it in org-
bibtex to generate the CUSTOM_ID?
2) It might be better to use the (generated) key as the Org headline,
instead of the title. Titles can be longer than I find comfortable
for an Org-mode headline, whereas keys are usually about the right
length.
3) org-bibtex-cite seems like a natural next step, especially if it
offers a list of keys in the Org-mode buffer.
Here are the details of my test run:
Existing bibtex entry:
@Book{tuggle94:_cultur_resour_naval_air_station_barber_point,
author ={H. David Tuggle and M. J. Tomonari-Tuggle and
D. Colt Denfeld},
title ={Cultural Resources of Naval Air Station, Barbers
Point: Summary, Assessment, and Inventory Research
Design: Task 1b: Archaeological Research Services
for the Proposed Cleanup, Disposal, and Reuse of
Naval Air Station, Barbers Point, O`ahu, Hawai`i},
publisher =iarii,
year = 1994,
series ={Prepared for Belt Collins Hawaii},
address = {Honolulu},
month = {December}}
Org-mode tree:
* Schulte bibtex
** A journal title
:PROPERTIES:
:type: article
:AUTHOR: A. N. Author
:JOURNAL: Journal of Statistical Software
:YEAR: 1998
:CUSTOM_ID: author_10:article
:END:
** {Cultural Resources of Naval Air Station, Barbers
:PROPERTIES:
:TYPE: book
:CUSTOM_ID: tuggle94:_cultur_resour_naval_air_station_barber_point
:MONTH:December}
:ADDRESS: Honolulu
:SERIES: Prepared for Belt Collins Hawaii
:YEAR: 1994
:PUBLISHER: iarii
:AUTHOR: {H. David Tuggle and M. J. Tomonari-Tuggle and
:END:
Org-bibtex output:
@book{tuggle94:_cultur_resour_naval_air_station_barber_point,
author={{H. David Tuggle and M. J. Tomonari-Tuggle and},
title={{Cultural Resources of Naval Air Station, Barbers},
publisher={iarii},
year={1994},
series={Prepared for Belt Collins Hawaii},
address={Honolulu},
month={December}}
}
hth,
Tom
On Apr 19, 2011, at 1:52 PM, Eric Schulte wrote:
Hi,
In an attempt to organize my reading notes, I've written the following
tool which allows both for exporting Org-mode headlines with bibtex
meta-data to bibtex entries, and for reading existing bibtex entries
into Org-mode headings.
One nice feature of these functions is the ability to check that all
required fields are present in a given headline based on the bibtex
type
(e.g., :article, :inproceedings), and prompt for missing fields.
See the top of the elisp file for more usage information.
https://github.com/eschulte/org-bibtex/blob/master/org-bibtex.el
Cheers -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
