Re: [O] How to get notify from Org-mode's clock, timestamps, and appointments etc with in modeline or with notify-send etc programs ?
chris numbch...@gmail.com writes: I want to good way to notify me about Org-mode's clock, timestamps, effort estimates and appointments etc with in Emacs's modeline or with notify programs like notify-send. And I hope this notify solution also can work for calendar events, new email's arrival, and IRC notification. (I know maybe there is no this ready-made solution) I know that Org-mode has a library called `org-clock` has a function `org-notify' can notify with program *notify-send*. I hope you can suggest some solutions, and provide some more details about your solution too. (Thanks in advanced) You might want to take a look at this library: https://github.com/djcb/sauron Regards, Alex
Re: [O] managing articles in my personal library, and their citational material, using org mode instead of bibtex
Eric Schulte schulte.e...@gmail.com writes:
Ian Barton li...@wilkesley.net writes:
On 19/11/13 01:40, Christopher W. Ryan wrote:
Not sure citational is even a word, but hopefully it conveys my meaning!
I've been using LaTeX for academic writing and reading for quite some
time, with emacs as my editor. I'm pretty familiar with managing a .bib
file containing all the references I've collected, and using it in LaTeX
\cite commands.
I've come to org-mode more recently. I'm trying to imagine how I might
use it to manage my personal library. I have a directory full of pdf
files, each a downloaded article. Some articles I reference in papers I
write; others I just read and want to keep. I also have a .bib file
where I put the citational material for all those articles. Whenever I
download an article, I add its entry to my .bib file. I tend to manage
this with JabRef because it searches Medline so easily, but I also will
edit the .bib file directly when necessary.
I like the idea of an org file containing the citational information
(authors, title, journal, etc) *plus* links to the pdfs on my hard
drive, or on the internet. I could also include my notes about the
articles. But what would that org file look like? How do I insert a
reference to an article into the org file which contains the article I
am writing?
I'd be grateful for any explanations, or links to tutorials.
I am also a grad student, and I use a setup which is similar to Eric's,
but rather than importing from bibtex, I use Org's capture features to
directly input the bibliographic data when I come across something I
want to add to my reading list. I don't maintain a separate .bib file
at all; rather I generate it as needed from the Org file containing my
reading list.
This setup allows me to think of readings as TODO items included in my
agenda, take notes and make links in the entry, and also keep
bibliographic data in Org (which I export via org-bibtex).
Here's what my setup looks like:
1) A capture template for new readings. My template looks like this:
** %^{Todo state|FIND|PRINT|READ|NOTES} [#%^{Priority|A|B|C}]
%^{Description|Reading} %^g
%^{TITLE}p %^{AUTHOR}p %^{AREA}p %?
:PROPERTIES:
:Entered: %U
:END:
This template does not have a field for adding links to PDFs, but you
could easily add that.
2) A hook to add bibliographic data to reading entries when finalizing a
capture. I put this in my Org setup:
;; post-processing in capture templates
(defun add-bibliographic-data ()
; this is a bit hacky: we detect the AUTHOR property, and create bibtex
entries if
; it is present
(message optionally adding bibliographic data)
(if (and (org-entry-get (point) AUTHOR)
(y-or-n-p Add bibliographic data? ))
; with prefix arg to get all fields:
(org-bibtex-create-in-current-entry 1)
nil))
(add-hook 'org-capture-before-finalize-hook (lambda ()
(add-bibliographic-data)))
There may be a better way to do this, but it works for me!
3) Elisp functions to export my entire reading list to .bib (these
assume that your readings are not in a separate file, but under a top-level
entry called Reading list in some other file):
;; lib/el/bib-export.el in my dissertation tree:
(setq dissertation-bib-file
~/Documents/philosophy/dissertation/build/dissertation.bib)
(defun add-headline-to-bib-buffer (bib-buffer)
Export headline at point to Bibtex into the given buffer
(let ((bib-entry (org-bibtex-headline))
(custom-id (org-entry-get (point) CUSTOM_ID)))
(if (and custom-id bib-entry)
(with-current-buffer bib-buffer
(insert bib-entry)
(defun export-subtree-to-bib-buffer (headline bib-buffer)
Export the entries in the subtree at point to Bibtex into the given buffer.
(save-excursion
(goto-char (org-find-exact-headline-in-buffer headline))
(org-map-entries
(lambda () (add-headline-to-bib-buffer bib-buffer))
t ; match: all entries below this one
'tree ; scope: just this subtree
)))
(defun reading-list-to-bibtex ()
Export 'Reading list' headline in current buffer to dissertation.bib
(interactive)
(let ((org-buffer (current-buffer))
(bib-buffer (create-file-buffer dissertation.bib)))
(export-subtree-to-bib-buffer Reading list bib-buffer)
(with-current-buffer bib-buffer
(write-file dissertation-bib-file
4) A Makefile entry to call the export functions:
BATCH_EMACS=$(EMACS) --batch -Q
bib: tasks.org lib/el/bib-export.el
$(BATCH_EMACS) --load lib/el/bib-export.el --file tasks.org --funcall
reading-list-to-bibtex
Thus, I can run make bib in my dissertation tree and get a fresh
export of all my readings to a .bib file.
Hope that helps!
Best,
Richard
Re: [O] Refresh buffer properties and local variables
Hi Nick, Nick Dokos ndo...@gmail.com writes: Looking at what normal-mode does, I came up with the following hack. Does it fix things for you? diff --git a/lisp/org.el b/lisp/org.el index febee75..caf0348 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -5512,7 +5512,8 @@ The following commands are available: (unless org-inhibit-startup-visibility-stuff (org-set-startup-visibility ;; Try to set org-hide correctly - (set-face-foreground 'org-hide (org-find-invisible-foreground))) + (set-face-foreground 'org-hide (org-find-invisible-foreground)) + (hack-local-variables)) ;; Update `customize-package-emacs-version-alist' (add-to-list 'customize-package-emacs-version-alist Yes, it seems to fix things for me. What an unfortunate function name! Thanks for your help. Is there something else I can do to get this change into Org? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Refresh buffer properties and local variables
Hi Thomas and Nick, t...@tsdye.com (Thomas S. Dye) writes: Thanks for your help. Is there something else I can do to get this change into Org? Nick, feel free to push this fix -- it was indeed not intended. Thanks! -- Bastien
[O] \newpage in HTML export
Both \newpage and #+LATEX: \newpage generate page breaks in Latex. However \newpage is included verbatim in HTML export. Should I use #+LATEX: \newpage instead? /Luke
[O] tricky odt export needs
Hi all, I have a document that was formerly a LaTeX file. In it there were labels and references using \label and \pageref. I am needing to export to doc using ox-odt. I have been able to do some fairly advanced things like using styles I've modified and created. But I'm having trouble with all but one of the techniques shown in Creating one-off styles in the manual. This includes the simplest solution, which has you prepend odt tags with @. So the example on that page: @text:span text:style-name=HighlightThis is a highlighted text@/text:span. But this is a regular text. doesn't work. That is, the resulting .odt file shows the text above with the @ symbols. Am I missing something? It would be nice to know how I can get embedded odt tags to work as described in the manual. But what's more important, and may make the odt tag question moot, is to be able to mark places in the document as labels and page references. Even if I could get just the first part of that going (marking certain places as labels or cross reference sources) then I'd be further along. Please note that the idea here is not to create labels for images or tables. What I am needing are labels that later would be used to create a cross reference to a page or footnote number. Any thoughts? Thanks, Dan Griswold Rochester, NY
Re: [O] Refresh buffer properties and local variables
I'll prepare a properly formatted patch later on tonight. Nick
[O] Links to headings not generated in Tables
I am unable to get links of the following type to appear in Tables when exporting to HTML or Latex; [[*Heading 1][A Heading]] The links are valid in Emacs, meaning I can navigate to the target using C-c C-o. Links to headings using ID, or links to other tables ( e.g. [[tbl:aTable]]) do seem to work. /Luke
Re: [O] \newpage in HTML export
This works well for me: #+HTML: div style=page-break-before: alwaysnbsp;/div placed right where you want the page break. The break will not appear in the browser, but it will when you print. Dan On Wed, Nov 20, 2013 at 1:52 PM, Luke Crook l...@balooga.com wrote: Both \newpage and #+LATEX: \newpage generate page breaks in Latex. However \newpage is included verbatim in HTML export. Should I use #+LATEX: \newpage instead? /Luke
Re: [O] tricky odt export needs
Hello, Dan Griswold dgris...@rochester.rr.com writes: @text:span text:style-name=HighlightThis is a highlighted text@/text:span. But this is a regular text. doesn't work. That is, the resulting .odt file shows the text above with the @ symbols. Am I missing something? Syntax for Org 8.0 is: @@odt:text:span text:style-name=Highlight@@ Regards, -- Nicolas Goaziou
Re: [O] Links to headings not generated in Tables
Hello, Luke Crook l...@balooga.com writes: I am unable to get links of the following type to appear in Tables when exporting to HTML or Latex; [[*Heading 1][A Heading]] The links are valid in Emacs, meaning I can navigate to the target using C-c C-o. Links to headings using ID, or links to other tables ( e.g. [[tbl:aTable]]) do seem to work. You are probably using an old Org revision (e.g. the one shipped with Emacs 24.3). Anyway, the problem doesn't seem to be in Org 8.0. Regards, -- Nicolas Goaziou
Re: [O] tricky odt export needs
Hi, @text:span text:style-name=HighlightThis is a highlighted text@/text:span. But this is a regular text. doesn't work. That is, the resulting .odt file shows the text above with the @ symbols. Am I missing something? No, the manual is. My bad, sort of; I meant to fix it a week ago but never got around to it. With the new exporter, the syntax is: @@odt:text:span text:style-name=Highlight@@This is a highlighted text@@odt:/text:span@@. But this is a regular text. The raw ODT is now wrapped in double @@'s, not preceded by a single @, and you need to specify the backend after the leading @@'s. It would be nice to know how I can get embedded odt tags to work as described in the manual. But what's more important, and may make the odt tag question moot, is to be able to mark places in the document as labels and page references. Even if I could get just the first part of that going (marking certain places as labels or cross reference sources) then I'd be further along. You can do cross-references with ordinary links. Have a look at the manual section 4.2, Internal links. However, what you get out of the box is textual references to e.g. section headings, not page references. You can change that for each reference individually by right-clicking on them in LibreOffice. There should be a way to get page references by default, but off the cuff, I'm not sure how. Yours, Christian
Re: [O] tricky odt export needs
Thank you, Nicolas! This is just what I need. It seems that my installation of org mode (from orgmode.org/elpa) does not have its info file updated to reflect that change of syntax. Dan On Wed, Nov 20, 2013 at 3:24 PM, Nicolas Goaziou n.goaz...@gmail.comwrote: Hello, Dan Griswold dgris...@rochester.rr.com writes: @text:span text:style-name=HighlightThis is a highlighted text@/text:span. But this is a regular text. doesn't work. That is, the resulting .odt file shows the text above with the @ symbols. Am I missing something? Syntax for Org 8.0 is: @@odt:text:span text:style-name=Highlight@@ Regards, -- Nicolas Goaziou
Re: [O] tricky odt export needs
Thank you Christian, This is very helpful. I'll do some comparing of the standard way of doing links with the workaround I've stumbled into. Cheers, Dan On Wed, Nov 20, 2013 at 3:34 PM, Christian Moe m...@christianmoe.comwrote: Hi, @text:span text:style-name=HighlightThis is a highlighted text@/text:span. But this is a regular text. doesn't work. That is, the resulting .odt file shows the text above with the @ symbols. Am I missing something? No, the manual is. My bad, sort of; I meant to fix it a week ago but never got around to it. With the new exporter, the syntax is: @@odt:text:span text:style-name=Highlight@@This is a highlighted text@@odt:/text:span@@. But this is a regular text. The raw ODT is now wrapped in double @@'s, not preceded by a single @, and you need to specify the backend after the leading @@'s. It would be nice to know how I can get embedded odt tags to work as described in the manual. But what's more important, and may make the odt tag question moot, is to be able to mark places in the document as labels and page references. Even if I could get just the first part of that going (marking certain places as labels or cross reference sources) then I'd be further along. You can do cross-references with ordinary links. Have a look at the manual section 4.2, Internal links. However, what you get out of the box is textual references to e.g. section headings, not page references. You can change that for each reference individually by right-clicking on them in LibreOffice. There should be a way to get page references by default, but off the cuff, I'm not sure how. Yours, Christian
Re: [O] Links to headings not generated in Tables
Nicolas Goaziou n.goaziou at gmail.com writes: You are probably using an old Org revision (e.g. the one shipped with Emacs 24.3). Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version.
Re: [O] tricky odt export needs
Dan Griswold dgris...@rochester.rr.com writes: It seems that my installation of org mode (from orgmode.org/elpa) does not have its info file updated to reflect that change of syntax. I updated the manual. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Links to headings not generated in Tables
Hello, Luke Crook l...@balooga.com writes: Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version. OK. Then could you provide an ECM? I'm unable to reproduce the problem. Regards, -- Nicolas Goaziou
Re: [O] \newpage in HTML export
That works. But that means I need both #+HTML: and #+Latex: for the same thing. \newpage should convert as appropriate depending on the export. So, \newpage should translate to the HTML equivalent on HTML export, and the Latex equivalent on Latex export. It only works correctly on Latex export
Re: [O] \newpage in HTML export
On Wed, Nov 20, 2013 at 09:15:43PM +, Luke Crook wrote: That works. But that means I need both #+HTML: and #+Latex: for the same thing. \newpage should convert as appropriate depending on the export. So, \newpage should translate to the HTML equivalent on HTML export, and the Latex equivalent on Latex export. It only works correctly on Latex export \newpage is a Latex command, and so you need the #+Latex: prefix if you're exporting to multiple formats. That will prevent it from happening. You could use both the #+Latex newpage and the #+HTML snippet together at the same point to have the same behavior in both modes. -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] tricky odt export needs
I said: You can do cross-references with ordinary links. Have a look at the manual section 4.2, Internal links. However, what you get out of the box is textual references to e.g. section headings, not page references. You can change that for each reference individually by right-clicking on them in LibreOffice. There should be a way to get page references by default, but off the cuff, I'm not sure how. Well, here's one way to get those page references, using filters: (defun my-odt-filter-pagerefs (text backend info) Make page references, not textual references in ODT export. (when (org-export-derived-backend-p backend 'odt) (replace-regexp-in-string text:reference-format=\text\ text:reference-format=\page\ text))) (add-to-list 'org-export-filter-link-functions 'my-odt-filter-pagerefs) (Whee! I just wrote my first export filter.) Org doesn't know what the page number will be, so when you open the document in e.g. LibreOffice, you still have to update fields (Tools Update) before you see page numbers. Yours, Christian
Re: [O] tricky odt export needs
Thank you! On Wed, Nov 20, 2013 at 4:10 PM, Nicolas Goaziou n.goaz...@gmail.comwrote: Dan Griswold dgris...@rochester.rr.com writes: It seems that my installation of org mode (from orgmode.org/elpa) does not have its info file updated to reflect that change of syntax. I updated the manual. Thank you. Regards, -- Nicolas Goaziou
Re: [O] \newpage in HTML export
On Wed, Nov 20, 2013 at 03:20:02PM -0600, Russell Adams wrote:
On Wed, Nov 20, 2013 at 09:15:43PM +, Luke Crook wrote:
That works. But that means I need both #+HTML: and #+Latex: for the same
thing. \newpage should convert as appropriate depending on the export.
So, \newpage should translate to the HTML equivalent on HTML export, and the
Latex equivalent on Latex export.
It only works correctly on Latex export
\newpage is a Latex command, and so you need the #+Latex: prefix if
you're exporting to multiple formats. That will prevent it from
happening.
To add a historical comment, eventhough Org claims to be backend
neutral, it treats LaTeX preferencially in practice. e.g. many common
LaTeX commands/macros are understood by Org.
Just follow what Russel said, put them both where you need a pagebreak.
Try this:
#+MACRO: pagebreak @@latex:\newpage@@ @@html:div style=page-break-before:
alwaysnbsp;/div@@
{{{pagebreak}}}
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] managing articles in my personal library, and their citational material, using org mode instead of bibtex
I once tried to do something similar in org mode, at the end I thought I
was doing twice the work, so I ended up with just one big .bib file.
I copy the bib info from the website and then I have a function to yank it
a little bit cleaner into my bib file, something like this:
(defun bibtex-yank-citation ()
Yanks a citation in a .bib file. Eliminates several fields,
removes the key for the entry, and changes the abstract field for
an annote field.
(interactive)
(goto-char (point-max))
(let ((position (point)))
(insert (current-kill 0))
(goto-char position)
(re-search-forward \\(@.+?{\\).+?, nil t)
(replace-match \\1, nil nil)
(goto-char position)
(while (re-search-forward % nil t)
(replace-match % nil nil))
(goto-char position)
(while (re-search-forward ’ nil t)
(replace-match ' nil nil))
(goto-char position)
(while (re-search-forward á nil t)
(replace-match {\'a} nil nil))
(goto-char position)
(while (re-search-forward é nil t)
(replace-match {\'e} nil nil))
(goto-char position)
(while (re-search-forward í nil t)
(replace-match {\'i} nil nil))
(goto-char position)
(while (re-search-forward ó nil t)
(replace-match {\'o} nil nil))
(goto-char position)
(while (re-search-forward ú nil t)
(replace-match {\'u} nil nil))
(goto-char position)
(while (re-search-forward ñ nil t)
(replace-match {~n} nil nil))
(goto-char position)
(while (re-search-forward ç nil t)
(replace-match {c{c}} nil nil))
(goto-char position)
(while (re-search-forward – nil t)
(replace-match - nil nil))
(goto-char position)
(delete-matching-lines
^[[:space:]]*\\(keywords\\)\\|\\(note\\)\\|\\(url\\)\\|\\(jstor\\)\\|\\(doi\\)\\|\\(issn\\)\\|\\(html\\)\\|\\(language\\)\\|\\(copyright\\)\\|\\(eprint\\))
(goto-char position)
(while (re-search-forward \\(^[[:space:]]*\\)abstract nil t)
(replace-match annote nil nil
It also removes the key, so that then I just add extra information into the
annote field and then I generate the key with C-c C-c (bibtex-clean-entry).
You can configure your key type very specifically. See all the variables
bibtex-autokey-
That takes care of the new bibtex entry without effort. Now I have
(defun bibtex-kill-ring-save-key ()
Kill-ring-save the bibtex key.
(interactive)
(let ((position (point)))
(if (not (eq (point-max) position))
(forward-char))
(search-backward-regexp ^@ nil nil)
(search-forward {)
(copy-region-as-kill (point)
(funcall (lambda ()
(search-forward ,)
(backward-char)
(point
(goto-char position)))
To save the key to the kill-ring, and then I save the paper with that
filename under a unique folder.
Finally I have a function that opens the respective pdf when the cursor is
within one entry. And keys for the functions, bound to Hyper keys:
(eval-after-load bibtex '(progn
(define-key bibtex-mode-map
(kbd H-y) 'bibtex-yank-citation)
(define-key bibtex-mode-map
(kbd H-r) 'bibtex-kill-ring-save-key)
(define-key bibtex-mode-map
(kbd H-o)
'bibtex-open-reference-at-point)))
I even have a similar function that I use globally:
(defun open-reference-at-point ()
(interactive)
(er/expand-region 2)
(let* ((beg (region-beginning))
(end (region-end))
(article-name (buffer-substring beg end)))
(call-process evince nil 0 nil
(concat ~/documents/references/articles/
article-name
.pdf)))
(keyboard-quit))
So if I am in LaTeX, it is enough to call open-reference-at-point over the
text in \cite{...} and the pdf opens automatically.
As you can see everything just depends on using one folder for all the
references, one file for all the bib entries and the same name of the key
dot pdf for the pdf name. And you end up with an automatically super good
documented bib file. Which is very handy when you call C-c [ in LaTeX
(reftex-citation) and just vaguely remember something about what you want
to cite. Also if you want to open a certain reference you can search your
well documented bib file and open the reference with one key.
One last thing to get navigation a la org mode (C-c C-p and C-c C-n) and
folding with TAB in your bib file:
(defun bibtex-previous-entry ()
Go to the previous bibtex entry.
Re: [O] \newpage in HTML export
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Wed, Nov 20, 2013 at 03:20:02PM -0600, Russell Adams wrote:
On Wed, Nov 20, 2013 at 09:15:43PM +, Luke Crook wrote:
That works. But that means I need both #+HTML: and #+Latex: for the same
thing. \newpage should convert as appropriate depending on the export.
So, \newpage should translate to the HTML equivalent on HTML export, and
the
Latex equivalent on Latex export.
It only works correctly on Latex export
\newpage is a Latex command, and so you need the #+Latex: prefix if
you're exporting to multiple formats. That will prevent it from
happening.
To add a historical comment, eventhough Org claims to be backend
neutral, it treats LaTeX preferencially in practice. e.g. many common
LaTeX commands/macros are understood by Org.
Just follow what Russel said, put them both where you need a pagebreak.
Try this:
#+MACRO: pagebreak @@latex:\newpage@@ @@html:div style=page-break-before:
alwaysnbsp;/div@@
{{{pagebreak}}}
Hope this helps,
Emacs already has the concept of the page-delimiter (defaults to ^L),
for page-related commands. I once floated the idea of making a
page-break a full org element, that could be handled differently by
different backends. I think I made it sound too complicated, though.
Anyway, that's still a possibility.
[O] Problems with org-bibtex
Hi there, I have decided to give org-bibtex a try. I have loaded it in my .emacs file, but whenever I copy a bibtex entry and try to use org-bibtex-yank I get the following error Symbol's function definition is void: bibtex-beginning-of-entry Could someone tell me what this mean and how to fix it. Thanks M
Re: [O] Problems with org-bibtex
Sorry about that, I agree I should know better. Here is the Backtrace that I got, Cheers, M Debugger entered--Lisp error: (void-function bibtex-beginning-of-entry) bibtex-beginning-of-entry() org-bibtex-read() org-bibtex-yank() call-interactively(org-bibtex-yank record nil) command-execute(org-bibtex-yank record) (progn (setq prefix-arg current-prefix-arg) (setq this-command chosen-item) (command-execute chosen-item (quote record))) (unwind-protect (progn (setq prefix-arg current-prefix-arg) (setq this-command chosen-item) (command-execute chosen-item (quote record))) (smex-rank chosen-item) (smex-show-key-advice chosen-item) (run-at-time 0.01 nil (function (lambda (cmd) (setq last-repeatable-command cmd))) chosen-item)) (if smex-custom-action (let ((action smex-custom-action)) (setq smex-custom-action nil) (funcall action chosen-item)) (unwind-protect (progn (setq prefix-arg current-prefix-arg) (setq this-command chosen-item) (command-execute chosen-item (quote record))) (smex-rank chosen-item) (smex-show-key-advice chosen-item) (run-at-time 0.01 nil (function (lambda (cmd) (setq last-repeatable-command cmd))) chosen-item))) (let ((chosen-item (intern (smex-completing-read commands initial-input (if smex-custom-action (let ((action smex-custom-action)) (setq smex-custom-action nil) (funcall action chosen-item)) (unwind-protect (progn (setq prefix-arg current-prefix-arg) (setq this-command chosen-item) (command-execute chosen-item (quote record))) (smex-rank chosen-item) (smex-show-key-advice chosen-item) (run-at-time 0.01 nil (function (lambda (cmd) (setq last-repeatable-command cmd))) chosen-item smex-read-and-run((toggle-debug-on-error org-mode org-capture global-hl-line-mode load-file hl-sentence-mode text-scale-increase org-bibtex-yank gtd org-bibtex-read org-bibtex-search marv:toggle-line-spacing dnotes org-bibtex org-mobile-push notes print-buffer ps-print-buffer org-bibtex-create org-insert-drawer org-mode-reftex-search org-beamer-export-to-pdf org-beamer-export-as-latex org-bibtex-import-from-file org-bibtex-export-to-kill-ring a cd 5x5 any arp dbx dig erc ert esv ftp gdb irc jdb man mpc pdb pwd rsh sdb xdb yow calc diff dirs ...)) (if (smex-already-running) (smex-update-and-rerun) (and smex-auto-update (smex-detect-new-commands) (smex-update)) (smex-read-and-run smex-ido-cache)) smex() call-interactively(smex nil nil) On Wed, Nov 20, 2013 at 11:00 PM, Jambunathan K kjambunat...@gmail.comwrote: Marvin Doyley marvin...@gmail.com writes: Symbol's function definition is void: bibtex-beginning-of-entry Whenever you get an error, do M-x toggle-debug-on-error and post the *Backtrace* buffer. I am still surprised why (even) regulars in this list fail to do it.
Re: [O] How to get notify from Org-mode's clock, timestamps, and appointments etc with in modeline or with notify-send etc programs ?
Excerpts from [ Alexander Baier ] On [2013-11-20 11:49:48 +0100]: chris numbch...@gmail.com writes: You might want to take a look at this library: https://github.com/djcb/sauron Regards, Alex This is really great. Thanks very much. -- [ stardiviner ] Kill the world if you want. That's it. IRC(freenode): stardiviner \\ Twitter: @numbchild \\ signature.asc Description: Digital signature
Re: [O] Refresh buffer properties and local variables
t...@tsdye.com (Thomas S. Dye) writes: Aloha all, I just discovered that refreshing buffer properties, C-c C-c at the top of my Org mode file, resets Local Variables to their default values (I think). At any rate, the Local Variables I set at the end of the file are changed by refreshing buffer properties. Is this intended? I end up running M-x normal-mode afterwards, which is sometimes difficult to remember. All the best, Tom Patch attached. From 5ea02285bacb9592b20c95d4797ca7c2ec68ecac Mon Sep 17 00:00:00 2001 From: Nick Dokos ndo...@gmail.com Date: Thu, 21 Nov 2013 00:30:05 -0500 Subject: [PATCH] Ensure that file local variables are set * lisp/org.el (org-mode): Call `hack-local-variables' at the end of `org-mode' to set file local variables. Cribbed from `normal-mode'. Reported by Tom Dye: C-c C-c on e.g an #+OPTIONS line would lose file local variable settings. --- lisp/org.el | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index febee75..8539f51 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -5512,7 +5512,10 @@ The following commands are available: (unless org-inhibit-startup-visibility-stuff (org-set-startup-visibility ;; Try to set org-hide correctly - (set-face-foreground 'org-hide (org-find-invisible-foreground))) + (set-face-foreground 'org-hide (org-find-invisible-foreground)) + ;; Make sure that file local variables are set. + (report-errors File local-variables error: %s +(hack-local-variables))) ;; Update `customize-package-emacs-version-alist' (add-to-list 'customize-package-emacs-version-alist -- 1.8.3.101.g727a46b -- Nick
Re: [O] Refresh buffer properties and local variables
Hi Nick, Nick Dokos ndo...@gmail.com writes: Patch attached. Looks good, please push! Thanks, -- Bastien
