Re: [O] Sticky agenda branch merged
Max Mikhanosha writes: Hi Max, > I had pushed a fix, which should fix `org-agenda-to-appt' Yes, it seems to work again. Thanks a lot, Tassilo
Re: [O] Frequent crashes of Emacs 24 on Mac OS X 10.7.3 due to org-mode
Dear Martyn,
thanks for helping.
3) 7.7: As far as I remember, I've been there.
2) 24.0.94.1: I've definitely been there -- didn't sort it out. I even wanted to
build Emacs on my own to see if that has an influence. But I obtained some
errors due to missing tools (starting with libgif/libungif but after I installed
that many other things appeared) and others also reported that it is not too
easy under Lion
(http://readystate4.com/2011/04/19/installing-latest-command-line-emacs-on-mac-os-x/).
1) .emacs: I've never seen .emacs in org-babel, sounds interesting. What I
typically do is some kind of "bisection" procedure to find the the bug (comment
out half of the code, test, find the buggy half...).
The part of my .emacs that concerns org-mode is (of course the problem could be
elsewhere but my suspicion would be it's in here):
,[ org-mode part of .emacs: ]
| ;; basics
| (require 'org-install); use org-mode
| (setq org-startup-indented 1); use indentation in org mode
| (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode)); open all .org files
in org-mode
| (setq org-agenda-files
| (list "~/org/agenda.org")); set up org agenda file
| (setq org-default-notes-file "~/org/agenda.org"); set up org notes file
(stores captured events -- also use agenda.org)
| (setq org-agenda-start-on-weekday nil); start agenda view on current day
| (setq org-agenda-span 14); agenda view: show 14 days by default
| (setq calendar-week-start-day 1); start week on Monday
|
| ;; suggested global org keys
| (global-set-key (kbd "C-c l") 'org-store-link)
| (global-set-key (kbd "C-c c") 'org-capture); for capturing new TODO
| (global-set-key (kbd "C-c a") 'org-agenda); for viewing your agenda
|
| ;; define capture templates (for C-c c)
| ;; see 9.1.3.1 in the org-mode manual
| ;; order:
| ;; 1) key: trigger of the capture task
| ;; 2) description: description to be shown during selection
| ;; 3) type: - entry: org-mode node with headline; put in as a child of the
target
| ;; - ..., see org-manual
| ;; 4) target: where the captured item should be placed
| ;;- file+headline "path-to-file" [empty defaults to
org-default-notes-file] "node name where to put in"
| ;; 5) template: string which specifies the look of the template
| ;; %? # place the point here after template insertion
| ;; \n # newline
| ;; %^T # prompt for date and time
| ;; %U # inactive time stamp with date and time
| ;; %(org-contacts-template-name) # tries to determine the name
from Gnus
| ;; %^g # prompt for tag
| ;; %(org-contacts-template-email) # tries to determine the email
address from Gnus
| (setq org-capture-templates
| '(("t" "TODO in ~/org/agenda.org -> Tasks" entry (file+headline
"~/org/agenda.org" "Tasks")
| "* TODO %?\nSCHEDULED: %^T\n%U")
| ("c" "Contact in ~/org/contacts.org -> Contact" entry (file+headline
"~/org/contacts.org" "Contact")
| "* %?%(org-contacts-template-name)%(org-contacts-template-email) %^g
| :PROPERTIES:
| :WORK:
| :HOME:
| :MOBILE:
| :LOCATION:
| :NOTE:
| :URL:
| :END:")))
|
| ;; set up org-contacts
| (require 'diary-lib); for making org-contacts anniversaries work
| (setq load-path (cons "~/.emacs.d/contacts" load-path))
| (require 'org-contacts)
| (setq org-contacts-files (quote ("~/org/contacts.org"))); set up org-contacts
file
|
| ;; make org-mode play nicely together with yasnippets
| ;; http://eschulte.me/emacs-starter-kit/starter-kit-org.html
| (defun yas/org-very-safe-expand ()
| (let ((yas/fallback-behavior 'return-nil)) (yas/expand)))
| (add-hook 'org-mode-hook
| (lambda ()
| ;; yasnippet (using the new org-cycle hooks)
| (make-variable-buffer-local 'yas/trigger-key)
| (setq yas/trigger-key [tab])
| (add-to-list 'org-tab-first-hook 'yas/org-very-safe-expand)
| (define-key yas/keymap [tab] 'yas/next-field)
| ))
`
Just a remark: The problem has nothing to do with Sweave (I just use Sweave for
some weeks now and the crashes I had long before). Last week a colleague
wanted to use my laptop and as soon as he hit the first button, Emacs
crashed (-- very annoying -- this was when I decided to try to track the
problem down). That's why I have trouble figuring out what it is (and I was
quite
"happy" to see "org-mode" popping up through Console.app as a reason -- at least
that gives a chance to track it down).
I'll further explore and get back to you (and the guys from Emacs bug tracker
who also are interested in this).
Cheers,
Marius
PS: I used the same .emacs on Ubuntu 11.10, only one line was changed (the
default font being changed from Menlo -- which is Mac-specific). I never
experienced a crash (although I just tried it for some hours, so I can't tell
for sure).
[O] Bug in org-diary (Bad sexp)?
I think there might be a bug related to the recent changes in the agenda code, since it has just appeared in the last days. The following are minimal steps: (Ubuntu 11.10, GNU Emacs 23.3.1 (i686-pc-linux-gnu, GTK+ Version 2.24.5) of 2011-08-14 on rothera, modified by Debian, Org version just pulled: Org-mode version 7.8.09 (release_7.8.09.230.gec7b)) With the following file, say simpleorg.el (setq debug-on-error t debug-on-signal nil debug-on-quit nil) (add-to-list 'load-path "~/Downloads/org-mode/lisp") (require 'org-install) and a ~/diary file containing only: &%%(org-diary) - and starting with 'emacs -Q -l simpleorg.el' Then M-x diary gives: Bad sexp at line 1 in ~/diary: (org-diary) For some reason I do not get a backtrace. Hopefully somebody will be able at least to reproduce! Best regards, Rafael
[O] footnotes and mouse
I use org-mouse.el and footnotes.[fn::Like this.] I find that clicking in the middle of a footnote will place point at the beginning of the footnote after the last colon. I expected it to put point at the clicked location. Also with footnotes[fn:1: Like this.] which Org seems to insert. This sometimes seems to tell you to edit the definition. I also find that clicking at the end of a #+HTML: line will fold the entire file if there is a sole subtree in the file. I will create an MCE at some point if nobody can reproduce. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] org-wikinodes - find files in a specific directory
Thanks Darlan, I'll try it out. - Marcelo. On Mon, Apr 16, 2012 at 9:23 AM, Darlan Cavalcante Moreira < darc...@gmail.com> wrote: > > Maybe a custom link type is enough for this. You can define a 'wiki' link > type with > #+LINK: wiki ~/Wiki_folder/%s > and then use [[wiki:something.org][description]] > > -- > Darlan > > At Fri, 13 Apr 2012 12:23:12 -0500, > Marcelo de Moraes Serpa wrote: > > > > [1 ] > > Also, I just found out org-wikinodes can't use filenames as basic data > > units. It'd be nice if it could. Would it be too hard to support such > > feature? Most of my wiki files do not start with a headlines of the same > > name, for example. > > > > On Fri, Apr 13, 2012 at 12:19 PM, Marcelo de Moraes Serpa < > > celose...@gmail.com> wrote: > > > > > Hi guys, > > > > > > Is it possible to setup wikinodes to find files in a specific directory > > > (rather than current file or current directory)? > > > > > > It'd also be nice if we could have a way to specify a list of > directories. > > > My org filesystem layout follows a particular convention where > "wiki-like" > > > (reference) files are kept in a directory of its own, but there are > some > > > exceptions to this rule - files in other dirs that I'd like wikinodes > to > > > take into consideration. > > > > > > Thanks! > > > > > > - Marcelo. > > > > > [2 ] > > >
Re: [O] Yearly repeats on the agenda
Copied a South African diary? :)
[O] Org-mode for Product Requirements
Hi Org-mode Community, I'm a product manager and I've been using org-mode for quite some time and was recently thinking how Org-mode might be a good starting point for a personal product requirements management system. I've searched around a bit and didn't find any discussions about such a topic, and before I start down this path I figured I'd send a note to this group to: a) See if anyone else uses org-mode for product requirements. I'd like to hear about that. b) Get feedback on my approach from other org-mode users. How I'm thinking of using properties, tags, TODO state, hooks, etc... I thought Org-mode would be a good place to start since, for me requirements are a bit like TODO items, I come across them during meetings with colleagues and customers and want to track them inline to the context that I find them in. I then want to take these "requirement" todo items and add a bit of structure and collect them in a different document. I'm leaning toward using a "requirement" tag on my TODO items since semantically the item is still a todo item, and the tag indicates a special way to handle that todo. I suppose the other way would be to create a new TODO state like REQ. Any reason why one would be better than the other? I'd probably start by hooking into org-after-todo-state-change-hook and looking for DONE and the requirement tag. And if I'm completing a TODO requirement then : 1. Choose the destination, maybe try and leverage existing "refiling" logic. 2. Copy the headline into the requirements document leaving behind the original completed headline and a link to the new requirement location. 3. Generate a file unique CUSTOM_ID like REQ-005 if this was the fifth requirement. This would allow for creating relationships between requirements without regard to their names. 4. Create the mandatory properties, perhaps this is just some type of template text for now, maybe a series of "wizard like" questions in the future. Then I'd also create a custom export option. Two things come to mind here in addition to what I already know about customizing html output. i. Formatting the properties in a specific order and in a custom way, emphasizing some properties over others. ii. How to get links in properties to work during html export like they do if you put a link in a text body. eg: in emacs [[#REQ-001]] displays as a link whether it's in a property or text body, but when exported as HTML only the one in the body text is an html link, the link in the property is just the original literal text [[#REQ-001]]. In the future I can see doing the following sorts of things: * Generating different views (both in emacs and for export) eg: roadmap view, filter by release, dependency tree view * Computing statistics like the number of requirements per release, amount of estimated engineering effort per release, etc... * Validate requirements checking for entries missing required properties, or entries that don't state something firm eg: has the words must or shall I'm only just beginning on this and I'd appreciate any feedback and advice the group may have. Best, ~>Bill Here's a sample of what I'm thinking in org mode format: * Introduction * Use Cases * Features ** Standard File Dialogs :PROPERTIES: :CUSTOM_ID: FEAT-001 :Topic: File IO :SolvedBy: [[#REQ-001]] [[#REQ-002]] :END: The product shall have standard file Open, Save, Save As features * Requirements :PROPERTIES: :Status_ALL: new reviewed approved assigned "in development" complete :END: ** Save as :PROPERTIES: :CUSTOM_ID: REQ-001 :Topic: File IO :Status: assigned :Release: Astraeus :Created: [2012-04-16 Mon] :Author: Bill Wishon :SolvedBy: [[#REQ-002]] :END: The product shall allow for users to save things to a different name. ** Save :PROPERTIES: :CUSTOM_ID: REQ-002 :Topic: File IO :DependsOn: [[#REQ-001]] :END: The product shall allow for users to save their work.
Re: [O] Yearly repeats on the agenda
SW wrote: > I have entries such as the following: > > *** <2011-01-01 +1y> New Year's Day :holiday: > > which appear on the agenda on the correct day each year, but they appear as: > > File: <2011-01-01 +1y> Public Holiday: Freedom Day :holiday: > > with the date showing. Other deadline/schedule/plain timestamp entries do not > show the full date. Which variable controls this? > Forget the date: is it really changing "New Year's Day" to "Public Holiday: Freedom Day" ?!?! Nick PS FWIW I can't reproduce either the date problem or the holiday name changing problem...
Re: [O] Sticky agenda branch merged
Max Mikhanosha writes: > I had pushed a fix, which should fix `org-agenda-to-appt' Thanks, it worked. Charles -- "The world is beating a path to our door" -- Bruce Perens, (Open Sources, 1999 O'Reilly and Associates) pgpS9uKFsMF8D.pgp Description: PGP signature
Re: [O] Sticky agenda branch merged
At Mon, 16 Apr 2012 19:44:54 +0200,
Tassilo Horn wrote:
>
> > I had just pushed a merge of max-sticky-agenda branch to master, let
> > me know if there are any problems,...
>
> since the merge, I get an error on emacs startup. The error is caused
> by invoking `org-agenda-to-appt' on emacs startup.
>
> Here's a backtrace:
>
> --8<---cut here---start->8---
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> org-agenda-new-marker(9228)
> byte-code("\306 ... VBV)\311\207" [s txt pos save-match-data-internal
> todo-state org-agenda-repeating-timestamp-show-all org-agenda-skip
> match-string 1 nil match-data ((byte-code "\301\302\"\207"
> [save-match-data-internal set-match-data evaporate] 3)) org-get-todo-state t
> org-time-string-to-absolute past 0 abs functionp org-is-habit-p
> org-get-category get-text-property org-category-position re-search-backward
> "^\\*+[]+" throw :skip assoc org-get-tags-at
> buffer-substring-no-properties "^\n" string-match "
> \\([012]?[0-9]:[0-9][0-9]\\)" " " time org-agenda-format-item format
> org-scheduled-previously org-scheduled-today org-scheduled
> org-habit-parse-todo org-add-props undone-face face org-agenda-done
> org-marker org-agenda-new-marker org-hd-marker type "past-scheduled" ...] 26)
> org-agenda-get-scheduled(nil)
I had pushed a fix, which should fix `org-agenda-to-appt'
Regards,
Max
[O] [latex, beamerposter] Muticolumn poster with multicolumn blocks or BMCOL and B_columns coexistance, is it possible?
All:
I realized I have a need for 2 columns in a block. However when I tried to use
B_columns and B_column besides BMCOL that were alreasy in there, it failed to
generate proper LaTeX source. Below is the trimmed down example that fails to
work properly on 7.8.09 . Do I miss something?
#-*- buffer-file-coding-system: utf-8; TeX-master: t -*-
#+Title: Test for multicolumn blocks in multicolumn poster
#+LaTeX_CLASS: beamer
#LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_FRAME_LEVEL: 1
#+STARTUP: beamer
#BEAMER_HEADER_EXTRA: \usetheme{I6dv} %mlt}
#\usecolortheme{default}
#+COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env Args)
%4BEAMER_col(Col) %8BEAMER_extra(Extra)
#+PROPERTY: BEAMER_col_ALL 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 :ETC
#+OPTIONS: toc:nil
#+latex_header:
\usepackage[orientation=landscape,size=custom,width=182.88,height=101.6,scale=1.5]{beamerposter}
#+LATEX_HEADER: \renewcommand\maketitle{}
# http://blog.zindel.org/?p=99
#+latex_header: \def\newblock{\hskip .11em plus .33em minus .07em}
# C-c C-x C-c for column view
* Poster
** Left :BMCOL:B_ignoreheading:
:PROPERTIES:
:BEAMER_col: 0.32
:BEAMER_env: ignoreheading
:END:
*** 1 Left :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
Columns :B_columns:
:PROPERTIES:
:BEAMER_env: columns
:END:
* .5 :B_column:
:PROPERTIES:
:BEAMER_env: column
:END:
- intro left. Comment stuff above till including Columns to make it compilable
* .4 :B_column:
:PROPERTIES:
:BEAMER_env: column
:END:
- intro right. Comment stuff above.
** Center :BMCOL:B_ignoreheading:
:PROPERTIES:
:BEAMER_col: 0.32
:BEAMER_env: ignoreheading
:END:
*** 2 Center:B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- Central block
** Right :BMCOL:B_ignoreheading:
:PROPERTIES:
:BEAMER_col: 0.32
:BEAMER_env: ignoreheading
:END:
*** 3 right block :B_block:
:PROPERTIES:
:BEAMER_env: block
:END:
- hello
Mikhail
[O] Yearly repeats on the agenda
I have entries such as the following: *** <2011-01-01 +1y> New Year's Day:holiday: which appear on the agenda on the correct day each year, but they appear as: File: <2011-01-01 +1y> Public Holiday: Freedom Day :holiday: with the date showing. Other deadline/schedule/plain timestamp entries do not show the full date. Which variable controls this?
Re: [O] Frequent crashes of Emacs 24 on Mac OS X 10.7.3 due to org-mode
Hi Marius Marius Hofert writes: > Hi, > > I work with GNU Emacs 24.0.95.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) > [installed as Emacs-pretest-24.0.95-universal-10.6.8 from > http://emacsformacosx.com/builds ] on Mac OS X 10.7.3. (The reason for Emacs > 24 > is because of the latest features in Gnus). The org-mode version I use is > 7.8.08. > > I frequently experience crashes of Emacs during various tasks (see > http://stackoverflow.com/questions/10164425/emacs-almost-random-crashes-about-2-3-times-a-day-on-mac-os-x#comment13039387_10164425 > which I posted earlier today when I didn't know the cause of the crashes). By > checking Console.app, I found what I also suspected: org-mode causes the > crashes. The problem is, I don't know how to solve this problem (I'm an > enthusiastic [although maybe not really experienced] org-mode user and would > *really* like to use org-mode in the future as well). My setup is as follows: Org-mode version 7.8.08 (release_7.8.03.594.g013d.dirty) GNU Emacs 24.0.94.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-02-28 on bob.porkrind.org ... and Emacs never crashes - never ever! I don't use Sweave. - can you isolate what you do most use in your .emacs (easy if it's written in Org-babel). - Revert to 7.7. ~ test - Revert to 24.0.94.1 (macforosx binary build) ~ test I use it all the time (mostly Emacs but in and out of Org and Babel constantly) and it's solid, so it's probably your configuration. Best, Martyn
Re: [O] Usage of disqus instead of mailinglist considered harmful
Brian van den Broek writes: > On 8 Apr 2012 13:44, "Karl Voit" > > > >> Oh I'd like to warn here: disqus is a private commercial company >> that wants to make money. >> >> Their strategy can (and will) change from one day to the other. > > An enthusiastic +1 from this largely lurking list member. > Some other options could be: - Roll our own commenting system (a quick github search found https://github.com/phusion/juvia) - Setup automatic backups of comments using the disqus API, http://docs.disqus.com/developers/export/ I can search around and setup a commenting engine server and try to integrate it into worg like disqus, but unless it's an official server it's not much better. If random server someone sets up suddenly disappears it's the same as disqus changing their business model. I guess maybe a server with automatic comment exporting to git or something? Or org-maintainer admin access to server? Both? -- Kyle Sexton
Re: [O] Usage of disqus instead of mailinglist considered harmful
> Karl Voit : > Mailinglists - though currently handled by gmane which is also a > company - Gmane isn't a company and does not handle the org mailing list(s). Gmane is one man that gets donated server location, old servers, and network hosting from his employer. And gmane is an email<->NNTP gateway that also works as a searchable archive accessible with NNTP and HTTP.
Re: [O] Brackets around title in HTML from org-e-html
On 16/04/2012 19:07, Jambunathan K wrote: Shaun Johnson writes: Hi, The appended org file when exported to HTML using org-e-html (via org-export-dispatch) has brackets around the title. The generated HTML is attached (t.html) as is a screenshot (t.png). How can I avoid these brackets being inserted? Fixed. Please pull again. Many thanks for the speedy response. Shaun.
Re: [O] Possible bug in parsing / clarification of syntax
Hi Bastien, I have to revoke my earlier statement. The patch does _not_ remove the TODO_ line from the agenda. I see no change at all. Cheers, Simon On 04/10/2012 07:31 PM, Bastien wrote: Hi Simon, Simon Thum writes: I have found some irritating behaviour, potentially a bug. I have a block agenda which goes like: tags-todo "@home&TODO=\"TODO\" and it displays a certain org line that reads TODO_ state triggers Can you try the following patch (against latest hotfix HEAD) and report? Charles, can you let me know if this breaks anything in your usage of `org-map-entries'? David's original fix want to the right direction, except that we also want to match "* TODO" as a headline. Thanks for testing this quite heavily.
Re: [O] Sticky agenda branch merged
Tassilo Horn writes:
> since the merge, I get an error on emacs startup. The error is caused
> by invoking `org-agenda-to-appt' on emacs startup.
You beat me to it. I am seeing the same thing.
Also, I am able to run the function manually if there is an Agenda
buffer. Without an Agenda buffer being up, I get:
,[ Backtrace ]
| Debugger entered--Lisp error: (error "Selecting deleted buffer")
| org-agenda-new-marker(2614)
| byte-code("\306 \210\307\310!\311\310\224S\312 \313\216\314 *
\315=\206 \f\235<\316\307\310!=\317=Z?@\205??\320WA?\320W\203\\\321?!BW\203\\@\203\\C\203c?\320U\203\312\212\fD\235\211E\203\212F\204\205?\320U\203\205\322\323!\203\212\323
\203\212\311\202C\322\323!\205\222\323 G\324
H\325`\326\"I\327\330\311\315#\204\254J\202C\320\225b\210\320\224KG\203\320L\203\310@\204\362M\203\362\331\332\311\"\210\202\362N\315=\204\341N\203\362A\203\362\333KO\"\211P\203\362\331\332\311\"\210\334
Q\335`\336\311w\210`\"R\337\340\"\203\310\224\311O\341PS\202\342S\343?\320U\203$T@\202.\344TA@\310?Z\"RHQ?\320U\205=S\311G&
\203\311G\204UA\203U\345\202_@\203^\346\202_\347+G\205h\350 G\351
U\352+\353E\203{\354\202}+\355\356\n!\357\356K!\360A\203\220\361\202\221\362\363A\203\234>\202\2363\364G\203\253\365G!\202\265\366\367\370?Z\371
!#\372H\326I\373G\304\f&\210VBV)\311\207" [s txt pos
save-match-data-internal todo-state org-agenda-repeating-timestamp-show-all
org-agenda-skip match-string 1 nil match-data ((byte-code "\301\302\"\207"
[save-match-data-internal set-match-data evaporate] 3)) org-get-todo-state t
org-time-string-to-absolute past 0 abs functionp org-is-habit-p
org-get-category get-text-property org-category-position re-search-backward
"^\\*+[ ]+" throw :skip assoc org-get-tags-at
buffer-substring-no-properties "^\n" string-match "
\\([012]?[0-9]:[0-9][0-9]\\)" " " time org-agenda-format-item format
org-scheduled-previously org-scheduled-today org-scheduled org-habit-parse-todo
org-add-props undone-face face org-agenda-done org-marker org-agenda-new-marker
org-hd-marker type "past-scheduled" ...] 26)
| org-agenda-get-scheduled(nil)
| org-agenda-get-day-entries("~/Desktop/Projects/plans/AreasofFocus.org" (4
16 2012) :deadline :scheduled :timestamp)
| apply(org-agenda-get-day-entries
"~/Desktop/Projects/plans/AreasofFocus.org" (4 16 2012) (:deadline :scheduled
:timestamp))
| org-agenda-to-appt(nil)
| call-interactively(org-agenda-to-appt t nil)
| execute-extended-command(nil)
| call-interactively(execute-extended-command nil nil)
`
Charles
--
"Nature abhors a Vacuum"
-- Brian Behlendorf on OSS (Open Sources, 1999 O'Reilly and Associates)
pgpqK9LHBnVbS.pgp
Description: PGP signature
Re: [O] Scientific papers related to Org-mode
"Sebastien Vauban"
writes:
> Hi Bastien,
>
> Bastien wrote:
>> #+begin_src emacs-lisp
>> (defun org-insert-manual-bitex-citation-at-point ()
>> "Insert a Bibtex citation of the Org manual at point."
>> (interactive)
>> (insert
>> "@book{dominik10:_org_mode_refer_manual,
>> author = {Carsten Dominik},
>> title ={The \pkg{Org-Mode} 7 Reference Manual: Organize
>> Your Life with GNU Emacs},
>> publisher ={Network Theory},
>> year = 2010,
>> address = {UK},
>> note = {with contributions by David O`Toole, Bastien Guerry,
>> Philip Rooke, Dan Davison, Eric Schulte, and Thomas
>> Dye}
>> }"
>> (message "Thanks for quoting the Org manual!")))
>> #+end_src
>
> Wouldn't it be David O'Toole instead? I mean: with a normal (or forward, at
> least) quote?
>
> Best regards,
> Seb
Aloha Seb,
Sharp eye! I found this error in two places on Worg, both fixed now.
Thanks.
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] Brackets around title in HTML from org-e-html
Shaun Johnson writes: > Hi, > > The appended org file when exported to HTML using org-e-html > (via org-export-dispatch) has brackets around the title. The > generated HTML is attached (t.html) as is a screenshot (t.png). > > How can I avoid these brackets being inserted? Fixed. Please pull again. > Thanks, > > Shaun. > > #+AUTHOR: Shaun Johnson > #+EMAIL: sh...@slugfest.demon.co.uk > #+TITLE: Mappers > #+OPTIONS: ^:nil author:t timestamp:t toc:t > #+DATE: %Y/%m/%d > #+BABEL: :comments link :mkdirp yes > * Overview > Blah, blah > > --
Re: [O] Sticky agenda branch merged
Max Mikhanosha writes:
Hi Max,
> I had just pushed a merge of max-sticky-agenda branch to master, let
> me know if there are any problems,...
since the merge, I get an error on emacs startup. The error is caused
by invoking `org-agenda-to-appt' on emacs startup.
Here's a backtrace:
--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
org-agenda-new-marker(9228)
byte-code("\306 ... VBV)\311\207" [s txt pos save-match-data-internal
todo-state org-agenda-repeating-timestamp-show-all org-agenda-skip match-string
1 nil match-data ((byte-code "\301\302\"\207" [save-match-data-internal
set-match-data evaporate] 3)) org-get-todo-state t org-time-string-to-absolute
past 0 abs functionp org-is-habit-p org-get-category get-text-property
org-category-position re-search-backward "^\\*+[ ]+" throw :skip assoc
org-get-tags-at buffer-substring-no-properties "^\n" string-match "
\\([012]?[0-9]:[0-9][0-9]\\)" " " time org-agenda-format-item format
org-scheduled-previously org-scheduled-today org-scheduled org-habit-parse-todo
org-add-props undone-face face org-agenda-done org-marker org-agenda-new-marker
org-hd-marker type "past-scheduled" ...] 26)
org-agenda-get-scheduled(nil)
org-agenda-get-day-entries("/home/horn/Repos/org/remember.org" (4 16 2012)
:deadline :scheduled :timestamp)
apply(org-agenda-get-day-entries "/home/horn/Repos/org/remember.org" (4 16
2012) (:deadline :scheduled :timestamp))
org-agenda-to-appt(t)
th-org-agenda-to-appt()
eval-buffer(# nil "/home/horn/.emacs" nil t) ; Reading at
buffer position 50862
load-with-code-conversion("/home/horn/.emacs" "/home/horn/.emacs" t t)
load("~/.emacs" t t)
#[0 "\205 ... \211#)\262\207" [init-file-user system-type
delayed-warnings-list user-init-file inhibit-default-init
inhibit-startup-screen ms-dos "~" "/_emacs" windows-nt "/.emacs"
directory-files nil "^\\.emacs\\(\\.elc?\\)?$" "~/.emacs"
"^_emacs\\(\\.elc?\\)?$" (initialization "`_emacs' init file is deprecated,
please use `.emacs'") "~/_emacs" t load expand-file-name "init"
file-name-as-directory "/.emacs.d" file-name-extension "elc"
file-name-sans-extension ".el" file-exists-p file-newer-than-file-p message
"Warning: %s is newer than %s" sit-for 1 "default"] 7 "\n\n(fn)"]()
command-line()
normal-top-level()
--8<---cut here---end--->8---
Please let me know if you need any further details.
Bye,
Tassilo
Re: [O] Bug: Footnotes badly positioned in HTML export [7.8.09 (release_7.8.09.234.g4a35)]
[Fwding to the list] Shaun Johnson writes: > On 16/04/2012 15:03, Jambunathan K wrote: >> Shaun Johnson writes: >> >>> On 16/04/2012 14:03, Shaun Johnson wrote: Hi, The attached example org file (t.org) with two footnotes generates the attached HTML file (t.html). As you can see in the attached screenshot (t.png) the footnote placement is odd to say the least. >>> >>> This problem doesn't org with the new exporter (org-export based) exporter >>> so I will probably go down that road. >> >> You mean org-e-html? > I mean: the problem does not occur with org-e-html. My last sentence in that mail should have read: This problem doesn't occur with the new exporter (org-export-dispatch based) so I will probably go down that road. Shaun.
Re: [O] org-wikinodes - find files in a specific directory
Maybe a custom link type is enough for this. You can define a 'wiki' link type with #+LINK: wiki ~/Wiki_folder/%s and then use [[wiki:something.org][description]] -- Darlan At Fri, 13 Apr 2012 12:23:12 -0500, Marcelo de Moraes Serpa wrote: > > [1 ] > Also, I just found out org-wikinodes can't use filenames as basic data > units. It'd be nice if it could. Would it be too hard to support such > feature? Most of my wiki files do not start with a headlines of the same > name, for example. > > On Fri, Apr 13, 2012 at 12:19 PM, Marcelo de Moraes Serpa < > celose...@gmail.com> wrote: > > > Hi guys, > > > > Is it possible to setup wikinodes to find files in a specific directory > > (rather than current file or current directory)? > > > > It'd also be nice if we could have a way to specify a list of directories. > > My org filesystem layout follows a particular convention where "wiki-like" > > (reference) files are kept in a directory of its own, but there are some > > exceptions to this rule - files in other dirs that I'd like wikinodes to > > take into consideration. > > > > Thanks! > > > > - Marcelo. > > > [2 ] >
Re: [O] [PATCH] Agenda: Fix org-agenda-bulk-toggle when point is at already marked item
Madan Ramakrishnan wrote: > Hi Nick, > Ah, of course, you're right; it would result in a change in behavior. > While I can certainly tweak the patch to maintain the old behavior > in the case of a negative or zero arg, stepping back, I don't quite > understand the reasoning for the current behavior. If a user has gone > to the trouble of providing a negative arg, it doesn't seem intuitive > that org-agenda-bulk-mark just does the same thing as if no negative > arg was passed in. > For what it's worth, the only caller that I see for this function in > the codebase is the one in org-agenda-bulk-toggle that I was aiming to > fix with this patch. Of course there could be folks relying on the > current behavior, but I'd be curious as to what they're looking to do. You are probably right and there probably is nobody who depends on the current behavior, but you never know for sure: that's the tyranny of backward compatibility. I'm certainly not using it in any strange way, so it's fine with me either way: I just wanted to point out the possibility. Nick > Madan R. > > On Mon, Apr 16, 2012 at 2:36 AM, Nick Dokos wrote: > > Madan Ramakrishnan wrote: > > > * lisp/org-agenda.el (org-agenda-bulk-mark): truly make arg optional > > as advertised by the function > > > > Problem here was that org-agenda-bulk-toggle calls org-agenda-bulk-mark > > with no parameters; however, the (max arg 1) call inside > > org-agenda-bulk-mark > > will fail with no parameter. Change the max to an or and all is well. > > > > This is my first patch for org so apologies for any inadvertent missteps > > > > TINYCHANGE > > --- > > lisp/org-agenda.el | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > > index 0ffaadb..4e9473d 100644 > > --- a/lisp/org-agenda.el > > +++ b/lisp/org-agenda.el > > @@ -8299,7 +8299,7 @@ This is a command that has to be installed in > > `calendar-mode-map'." > > (defun org-agenda-bulk-mark (&optional arg) > > "Mark the entry at point for future bulk action." > > (interactive "p") > > - (dotimes (i (max arg 1)) > > + (dotimes (i (or arg 1)) > > (unless (org-get-at-bol 'org-agenda-diary-link) > > (let* ((m (org-get-at-bol 'org-hd-marker)) > > ov) > > -- > > 1.7.9.2 > > > > I presume arg can be negative or zero. > > If arg is e.g. -3 > > (max arg 1) -> 1 > (or arg 1) -> -3 > > so your patch changes the behavior of the function > in these cases. > > Nick > > > > Alternatives: > >
Re: [O] Bug: Footnotes badly positioned in HTML export [7.8.09 (release_7.8.09.234.g4a35)]
Shaun Johnson writes: > On 16/04/2012 14:03, Shaun Johnson wrote: >> Hi, >> >> The attached example org file (t.org) with two footnotes generates the >> attached HTML file (t.html). As you can see in the attached screenshot >> (t.png) the footnote placement is odd to say the least. > > This problem doesn't org with the new exporter (org-export based) exporter > so I will probably go down that road. You mean org-e-html? > Shaun. > > --
Re: [O] Bug: Footnotes badly positioned in HTML export [7.8.09 (release_7.8.09.234.g4a35)]
On 16/04/2012 14:03, Shaun Johnson wrote: Hi, The attached example org file (t.org) with two footnotes generates the attached HTML file (t.html). As you can see in the attached screenshot (t.png) the footnote placement is odd to say the least. This problem doesn't org with the new exporter (org-export based) exporter so I will probably go down that road. Shaun.
Re: [O] Agenda filter for a specific file
Hi Marcelo and Bernt, Bernt Hansen wrote: > Marcelo de Moraes Serpa writes: >> Is there a way to define an agenda filter that will search in only one of >> the agenda files? The reason I do that is because although I have several >> files added to the agenda, only one contains "actionable items" (gtd.org). > > There are multiple ways to do this. > > 1) visit the file and restrict agenda view to the file with C-u C-c C-x < > > 2) set org-agenda-files for some custom-agenda-command just to use this > one file For the sake of completeness, a third one: 3) visit the file and do a limited search with `C-c a < s', that is inserting `<' after `C-c a' to limit the search for *that* agenda command only. Best regards, Seb -- Sebastien Vauban
Re: [O] bug#11249: 24.1.50; Overlay with face property causes calendar buffer to scroll
On Mon, Apr 16, 2012 at 05:50:50AM +0300, Eli Zaretskii wrote: > > Date: Sun, 15 Apr 2012 23:04:16 +0200 > > Cc: 11...@debbugs.gnu.org, emacs-orgmode@gnu.org > > From: Toby Cubitt > > > > The obvious solution is for org-mode to use a face that doesn't enlarge > > the characters. > > Another solution would be to enlarge the calendar window by one line. I've attached a patch that does exactly this. As expected, it fixes the bug for me. As discussed previously, the alternative solution would be to change the default face used to highlight the current date to something that doesn't set the :bold attribute (which would probably mean introducing a separate face for this, instead of reusing org-warning). But expanding the calendar window is a more general solution, as it fixes the problem for (almost) any face. Arguably, it might be worth defining a separate face for highlighting the date in the calendar during org-read-date, even if this patch is applied, so that it can be customized separately from the face for impending todo deadlines etc. If there's interest in adding a new calendar-date-highlight face, I can post a separate patch for that. For the record, one can already change the face used to highlight the date in the calendar from within .emacs, via (overlay-put org-date-ovl 'face 'new-face) But that's much less discoverable than defining a separate face for this. Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org >From 107b18f3ee306c0cd28566c8e7e5ba94c4b9268c Mon Sep 17 00:00:00 2001 From: "Toby S. Cubitt" Date: Mon, 16 Apr 2012 14:22:35 +0200 Subject: [PATCH] Enlarge calendar by 1 line to fix scrolling bug when selecting date. * lisp/org.el (org-read-date): Enlarge calendar window by 1 line, and make cursor invisible. --- lisp/org.el |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 170ddc9..18ae685 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -15106,6 +15106,8 @@ user." (save-excursion (save-window-excursion (calendar) + (org-eval-in-calendar + '(progn (enlarge-window 1) (setq cursor-type nil))) (unwind-protect (progn (calendar-forward-day (- (time-to-days org-def) -- 1.7.8.5
Re: [O] [PATCH] Allow more control over inserted whitespace in capture templates
Was there any feedback on this patch, or did it get lost in the noise?
At least for me, org-capture breaks the document heading layout by
inserting incorrect amounts of whitespace. And there's no way to
configure capture templates to make it work correctly.
The patch I posted fixes this behaviour.
(Or am I missing some already-existing way of doing this? See below for a
detailed description of the problem.)
Toby
On Mon, Feb 13, 2012 at 01:26:09PM +0100, Toby Cubitt wrote:
> When capturing an item as a subheading, the capture template :empty-lines
> property is not sufficient to ensure the correct document layout is
> maintained after capturing.
>
> This patch fixes the capture behaviour to insert new subheadings
> immediately after the previous heading (rather than immediately before
> the next one). And it adds new :empty-lines-before and :empty-lines-after
> capture template properties. (I can split these two changes into
> separated patches, if desired.)
>
> When set, the new :empty-lines-before and :empty-lines-after properties
> take precedence over :empty-lines in determining the amount of whitespace
> to add before or after the captured item, respectively. Together, these
> changes allow the correct document layout to be achieved after capturing,
> without any manual editing.
>
> (Since the whole idea of org-capture is to rapidly capture new ideas or
> todos, having to manually edit whitespace after capturing to fix the
> document layout is far from ideal.)
>
>
> To give a more detailed example of why I think these changes are needed,
> consider for example an org-mode document in which headings are separated
> by two empty lines, and subheadings are separated by a single empty
> line. (This is a natural layout if one wants headings to be separated by
> whitespace when folded, but subheadings not to be separated when folded):
>
>
> * heading 1
> ** subheading 1.1
>
> ** subheading 1.2
>
>
> * heading 2
> ** subheading 2.1
>
>
> Let's say I want add a captured item as a new "subheading 1.3" under
> "heading 1", preserving this layout structure. Then we need to add the
> new item immediately after "subheading 1.2", inserting one empty line
> before and two empty lines after. There appears to be no way to do this
> using :empty-lines.
>
> In fact, the existing implementation adds the new capture item
> immediately *before* the *following* heading ("heading 2" in this case),
> which seems to be altogether wrong, as it effectively forces two empty
> lines before the new item, regardless of the :empty-lines setting.
>
> Currently, setting :empty-lines to 0 leaves the document looking like
> this:
>
>
> * heading 1
> ** subheading 1.1
>
> ** subheading 1.2
>
>
> ** subheading 1.3
> * heading 2
> ** subheading 2.1
>
>
> whilst setting :empty-lines to 1 leaves the document looking like this:
>
>
> * heading 1
> ** subheading 1.1
>
> ** subheading 1.2
>
>
>
> ** subheading 1.3
>
> * heading 2
> ** subheading 2.1
>
>
> neither of which are likely to ever be what we want.
>
> With this patch, setting the new :empty-lines-before to 1 and
> :empty-lines-after to 2 results in the correct structure after capturing:
>
>
> * heading 1
> ** subheading 1.1
>
> ** subheading 1.2
>
> ** subheading 1.3
>
>
> * heading 2
> ** subheading 2.1
>
>
>
> I think this patch is largely orthogonal to the recent "removing
> whitespace from new captures" patch (currently in patchwork). That patch
> causes `whitespace-cleanup' to be called in the CAPTURE buffer before
> finalizing, which doesn't affect the additional whitespace inserted later
> on by the :empty-lines property. This patch allows more control over the
> latter, by providing a fairly simple extension of the existing
> :empty-lines property.
>
> Toby
--
Dr T. S. Cubitt
Mathematics and Quantum Information group
Department of Mathematics
Complutense University
Madrid, Spain
email: ts...@cantab.net
web: www.dr-qubit.org
Re: [O] Scientific papers related to Org-mode
Hi Bastien,
Bastien wrote:
> #+begin_src emacs-lisp
> (defun org-insert-manual-bitex-citation-at-point ()
> "Insert a Bibtex citation of the Org manual at point."
> (interactive)
> (insert
> "@book{dominik10:_org_mode_refer_manual,
> author = {Carsten Dominik},
> title ={The \pkg{Org-Mode} 7 Reference Manual: Organize
> Your Life with GNU Emacs},
> publisher ={Network Theory},
> year = 2010,
> address = {UK},
> note = {with contributions by David O`Toole, Bastien Guerry,
> Philip Rooke, Dan Davison, Eric Schulte, and Thomas
> Dye}
> }"
> (message "Thanks for quoting the Org manual!")))
> #+end_src
Wouldn't it be David O'Toole instead? I mean: with a normal (or forward, at
least) quote?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [PATCH] Agenda: Fix org-agenda-bulk-toggle when point is at already marked item
Hi Nick, Ah, of course, you're right; it would result in a change in behavior. While I can certainly tweak the patch to maintain the old behavior in the case of a negative or zero arg, stepping back, I don't quite understand the reasoning for the current behavior. If a user has gone to the trouble of providing a negative arg, it doesn't seem intuitive that org-agenda-bulk-mark just does the same thing as if no negative arg was passed in. For what it's worth, the only caller that I see for this function in the codebase is the one in org-agenda-bulk-toggle that I was aiming to fix with this patch. Of course there could be folks relying on the current behavior, but I'd be curious as to what they're looking to do. Madan R. On Mon, Apr 16, 2012 at 2:36 AM, Nick Dokos wrote: > Madan Ramakrishnan wrote: > > > * lisp/org-agenda.el (org-agenda-bulk-mark): truly make arg optional > > as advertised by the function > > > > Problem here was that org-agenda-bulk-toggle calls org-agenda-bulk-mark > > with no parameters; however, the (max arg 1) call inside > > org-agenda-bulk-mark > > will fail with no parameter. Change the max to an or and all is well. > > > > This is my first patch for org so apologies for any inadvertent missteps > > > > TINYCHANGE > > --- > > lisp/org-agenda.el |2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > > index 0ffaadb..4e9473d 100644 > > --- a/lisp/org-agenda.el > > +++ b/lisp/org-agenda.el > > @@ -8299,7 +8299,7 @@ This is a command that has to be installed in > > `calendar-mode-map'." > > (defun org-agenda-bulk-mark (&optional arg) > >"Mark the entry at point for future bulk action." > >(interactive "p") > > - (dotimes (i (max arg 1)) > > + (dotimes (i (or arg 1)) > > (unless (org-get-at-bol 'org-agenda-diary-link) > >(let* ((m (org-get-at-bol 'org-hd-marker)) > > ov) > > -- > > 1.7.9.2 > > > > I presume arg can be negative or zero. > > If arg is e.g. -3 > > (max arg 1) -> 1 > (or arg 1) -> -3 > > so your patch changes the behavior of the function > in these cases. > > Nick >
Re: [O] [babel] eval code only once :eval once
Hi Thomas,
Thomas S. Dye wrote:
> Torsten Wagner writes:
>> I started to use lisp (as well as other) code blocks more and more to
>> modify my work environment (emacs) for a particular (buffer-based)
>> task.
>> That is I change some variables, add some stuff etc.
>> A real world example is for example the section below
>>
>> * Set-up :nonexport:
>> #+source: setup-minted
>> #+begin_src emacs-lisp :exports none :results silent
>> (setq org-export-latex-listings 'minted)
>> (setq org-export-latex-custom-lang-environments
>> '(
>>(emacs-lisp "common-lispcode")
>> ))
>> (setq org-export-latex-minted-options
>> '(("frame" "lines")
>> ("fontsize" "\\scriptsize")
>> ("linenos" "")))
>> (setq org-latex-to-pdf-process
>> '("pdflatex -shell-escape -interaction nonstopmode
>> -output-directory %o %f"
>> "pdflatex -shell-escape -interaction nonstopmode
>> -output-directory %o %f"
>> "pdflatex -shell-escape -interaction nonstopmode
>> -output-directory %o %f"))
>> #+end_src
>>
>> This are settings from worg, which I use only during my work on that
>> particular file/buffer e.g. to modify the export of the following
>> beamer presentation.
>> Whenever I load the buffer I jump to set-up and hit C-c C-C to execute
>> it once. After that exports will do what I want.
>> If I would change the above to :exports results and :results silent I
>> would be asked to execute the code block on every export.
>> Thanks to the new auto completion feature, I came across :eval and
>> wonder if it makes sense to add
>> :eval once
>> and
>> :eval once-query
>>
>> Which would allow to execute it only once (with query) if not called
>> before and otherwise keeps quite.
>> That would make *Set-up blocks much more efficient.
>> Was thinking why there is no 'no-query' resp. 'always' flag which
>> would execute code blocks without query even if asked for it in
>> general but that would be somehow against safety measures ;)
>
> Aloha Totti,
>
> Will :cache yes do what you want?
I'd answer no, as this wouldn't be re-eval'ed the next time he opens that
buffer.
But...?
Best regards,
Seb
--
Sebastien Vauban
[O] Sticky agenda branch merged
I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max
