Re: [O] Preventing Org from being installed by elpa
On 12/21/2016 10:25 PM, Karl Voit wrote:
* Christian Wittern wrote:
On 12/21/2016 05:07 AM, Karl Voit wrote:
I got the tipp of creating «~/.emacs.d/elpa/org-3101/org-pkg.el»
with:
(define-package "org" "3101" "Dummy org mode package" 'nil)
And this simulates the fulfilled dependency so that my git version
of Org-mode is the only one installed (besides maybe the default one
from Emacs).
Hmm, this sounds like what I want. However, when I try this, Emacs tells me:
(file-error "Cannot open load file" "no such file or directory"
"/home//.emacs.d/elpa/org-3101/org-autoloads")
load("/home//.emacs.d/elpa/org-3101/org-autoloads" nil t)
Is there a way to avoid this?
I'm sorry.
Usually, I do keep detailed notes on things I do. But when I created
this pseudo-package, I did not write down a detailed howto for my
future me.
But the input for this came from this mailing list. So please search
the archive and you might get the original instructions.
OK, I found the source in this message by Alan Schmitt, to which you replied:
On 2016-01-28 12:33, Karl Voit writes:
>> I’ve had issues with this in the past (I also use org for git). To
>> make sure org is never installed with elpa, I manually install
>> (`package-install-file') this org.el file:
>>
>> #+begin_src emacs-lisp
>> ;;; org.el --- Dummy org mode package
>>
>> ;; Copyright (C) 2014 Alan Schmitt
>>
>> ;; Version: 3101
>>
>> ()
>>
>> ;;; org.el ends here
>> #+end_src
>
> There is no "(provide 'org)" or so?
I have not found it necessary. I make sure I load org before
initializing packages, and everything works.
Alan
Using this recipe, I get also a file org-autoloads.el produced by package.el
and everything seems to work.
Cheers,
Christian
--
Christian Wittern, Kyoto
[O] Org-moblie-push
I am on a Mac running emacs 25.1.1 with org 9.0.2 I am trying to configure mobile org. When I enter M-x org-mobile-push it returns nothing. What is the problem?
Re: [O] heading specific fast keys?
Thanks for the idea. It got me to read how org does it in the first
place ;)
Here is my solution at the moment. I just add a hook to
org-speed-command-hook, define special elfeed fast keys, and then when
on an ELFEED entry, get those first.
This is proof of concept code that works, and defaults to user then
default keys. What a great ecosystem org is!
Happy holidays everyone!
#+BEGIN_SRC emacs-lisp
(defun org-speed-elfeed (keys)
(when (or (and (bolp) (looking-at org-outline-regexp)
(not (null (org-entry-get (point) "ELFEED"
(and (functionp org-use-speed-commands)
(funcall org-use-speed-commands)))
(cdr (assoc keys(append
org-speed-commands-elfeed
org-speed-commands-user
org-speed-commands-default)
(setq org-speed-commands-elfeed
'(("b" . (lambda (&optional arg)
(save-excursion
(re-search-forward "Link: *")
(org-open-at-point-global))
(add-hook 'org-speed-command-hook 'org-speed-elfeed)
#+END_SRC
Cook, Malcolm writes:
> > -Original Message-
> > From: Emacs-orgmode [mailto:emacs-orgmode-
> > bounces+mec=stowers@gnu.org] On Behalf Of John Kitchin
> > Sent: Wednesday, December 21, 2016 2:18 PM
> > To: emacs-orgmode@gnu.org
> > Subject: [O] heading specific fast keys?
> >
> > I wondered if anyone know a straight forward way to make
> > heading-specific fast keys in org-mode.
> >
> > The idea is if I am on a heading that is a "contact" (which means it has
> > an EMAIL property), then there would be special hot keys for it, e.g.
> > "e" would compose a message, "u" might open a URL if it had one, etc...
> >
> > Or, on entries captured from elfeed, I could just press "b" to open the
> > entry in a browser, etc...
> >
> > I guess there would need to be some kind of hook that looks up a keymap
> > or something on these special positions. And maybe a default map for
> > non-special headings.
> >
> > Thoughts?
>
> Possible synergy from one of the approaches to
> [MultipleModes](https://www.emacswiki.org/emacs?search=%22MultipleModes%22)
>
> I use polymode in org-mode to good effect within which switches mode with
> code blocks to be language specific.
>
> It might suggest an architecture
>
>
>>
> > --
> > Professor John Kitchin
> > Doherty Hall A207F
> > Department of Chemical Engineering
> > Carnegie Mellon University
> > Pittsburgh, PA 15213
> > 412-268-7803
> > @johnkitchin
> > http://kitchingroup.cheme.cmu.edu
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
Re: [O] heading specific fast keys?
> -Original Message- > From: Emacs-orgmode [mailto:emacs-orgmode- > bounces+mec=stowers@gnu.org] On Behalf Of John Kitchin > Sent: Wednesday, December 21, 2016 2:18 PM > To: emacs-orgmode@gnu.org > Subject: [O] heading specific fast keys? > > I wondered if anyone know a straight forward way to make > heading-specific fast keys in org-mode. > > The idea is if I am on a heading that is a "contact" (which means it has > an EMAIL property), then there would be special hot keys for it, e.g. > "e" would compose a message, "u" might open a URL if it had one, etc... > > Or, on entries captured from elfeed, I could just press "b" to open the > entry in a browser, etc... > > I guess there would need to be some kind of hook that looks up a keymap > or something on these special positions. And maybe a default map for > non-special headings. > > Thoughts? Possible synergy from one of the approaches to [MultipleModes](https://www.emacswiki.org/emacs?search=%22MultipleModes%22) I use polymode in org-mode to good effect within which switches mode with code blocks to be language specific. It might suggest an architecture > > -- > Professor John Kitchin > Doherty Hall A207F > Department of Chemical Engineering > Carnegie Mellon University > Pittsburgh, PA 15213 > 412-268-7803 > @johnkitchin > http://kitchingroup.cheme.cmu.edu
[O] heading specific fast keys?
I wondered if anyone know a straight forward way to make heading-specific fast keys in org-mode. The idea is if I am on a heading that is a "contact" (which means it has an EMAIL property), then there would be special hot keys for it, e.g. "e" would compose a message, "u" might open a URL if it had one, etc... Or, on entries captured from elfeed, I could just press "b" to open the entry in a browser, etc... I guess there would need to be some kind of hook that looks up a keymap or something on these special positions. And maybe a default map for non-special headings. Thoughts? -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] how to convert/normalize plain footnotes into [fn:] ones
Hello, Gerald Wildgruber writes: > I had actually tried that already and came up with the following regex: > > \([^ ]\)\(\[\)\([0-9]\) --> \1\2fn:\3 > > i.e. three groupings: 1) no whitespace, 2) "[" and 3) a number, and then > introducing "fn:" between "[" and the number: but it is not perfect, as > it still gives false positives; do you have something better? I would use (and, in fact, used) \\[\\([0-9]+\\)\\] --> \\[fn:\\1\\] and eyeballing the results. > The problem unfortunately arises also by pandoc still using the now > obsolete syntax of plain footnotes when converting (e.g. latex) to org > mode! I'm certain Pandoc importer will ultimately catch-up. Regards, -- Nicolas Goaziou
Re: [O] sending an email to an orgmode file?
On Wednesday, 21 Dec 2016 at 17:18, Richard Lawrence wrote:
[...]
> In my own setup, I've settled on just making it easy to linking to an
> email from a new TODO entry. This is a very general mechanism that
> works well for me, even though it is not completely automatic. I
> describe my setup below.
I do the same thing, using the following template for org-capture which
creates a task:
#+begin_src emacs-lisp
("mt"
"mailtodo"
entry (file+datetree "~/s/notes/tasks.org")
"* TODO %^{Task} : %:subject %^G\nSCHEDULED: %t\n- From :: %:from\n- Subject
:: %:subject\n- Email :: %a\n\n%?"
:kill-buffer t)
#+end_src
I have an equivalent capture template for notes based on emails.
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.2-104-gf5b7de
signature.asc
Description: PGP signature
Re: [O] [ANN] Add EXPORT_FILE_NAME keyword
Nicolas Goaziou writes: > >> Similar to ~:EPORT_FILE_NAME:~ property, this keyword allows the user >> to specify the name of the output file upon exporting the document. >> This also has an effect on publishing (or "This also effects >> publishing." > > Of course. Thank you. IMO, the alternative wording here changes the meaning. The equivalent to "this also has an effect on publishing" would be "this also affects publishing." All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] sending an email to an orgmode file?
Hi Xebar,
Xebar Saram writes:
> im looking for a simple solution that will allow me to send an email from
> my mobile phone and habr that email either be appended to a txt(org) file
> or perhaps another solution to get my mobile on the go notes onto my laptop
> orgmode file. i tried orgzly and mobile org but i would prefer a simple
> solution as to send an email
>
> anyone have any thoughts on this?
I'd say a lot depends on the mail setup you use on the machine where
you use Org. Emacs-based mail clients will be easier to integrate with
Org. But really you're just limited by how much effort you want to sink
into this, at least if you store your mail in some format that is easy
to read with various tools.
If you use Gnus, one solution (I think?) is Gnorb:
https://elpa.gnu.org/packages/gnorb.html
I don't actually use this or know much about it but other people on this
list can tell you more about it.
In my own setup, I've settled on just making it easy to linking to an
email from a new TODO entry. This is a very general mechanism that
works well for me, even though it is not completely automatic. I
describe my setup below.
I use the Emacs interface for notmuch as my mail client. I integrate it
with Org via org-notmuch and Org capturing. Basically, I have a key that
automates capturing an email as a TODO item, containing a link to the
relevant mail:
#+BEGIN_SRC elisp
;; in my Org setup:
(require 'org-notmuch)
(setq org-capture-templates
; ...
`(("t" "Task, Note, Project, etc.")
("tm" "Mail" entry
(file ,(concat org-directory "/refile.org"))
(file ,(concat org-template-directory "/mail-with-link.txt")
;; in my notmuch setup:
(define-key notmuch-search-mode-map "P"
(lambda ()
"postpone message (remove inbox tag, create task to reply)"
(interactive)
(notmuch-search-tag '("-inbox" "-unread"))
(notmuch-search-show-thread)
(org-capture nil "tm")))
#+END_SRC
The mail-with-link.txt template is simple:
#+BEGIN_SRC org
* %a:MAIL:
:PROPERTIES:
:Entered: %U
:END:
%?
#+END_SRC
I mostly use this to record emails that I need to *reply* to as TODO
items, so a link to the original mail is enough for me.
This probably isn't quite what you're looking for, but with more effort
on the notmuch side, a setup like this could be used to extract the
content of the email into the Org capture. And you could also automate
this by looping over the messages that match a certain notmuch query,
etc.
HTH,
Richard
Re: [O] how to convert/normalize plain footnotes into [fn:] ones
Hi Nicolas, thanks: I had actually tried that already and came up with the following regex: \([^ ]\)\(\[\)\([0-9]\) --> \1\2fn:\3 i.e. three groupings: 1) no whitespace, 2) "[" and 3) a number, and then introducing "fn:" between "[" and the number: but it is not perfect, as it still gives false positives; do you have something better? The problem unfortunately arises also by pandoc still using the now obsolete syntax of plain footnotes when converting (e.g. latex) to org mode! Gerald. On Mi, Dez 21 2016, Nicolas Goaziou wrote: > Hello, > > Gerald Wildgruber writes: > >> I'm trying to convert older orgmode documents which have plain, >> "[1]"-like footnotes into the newer "[fn:]" format. >> >> Can this be done automatically? > > You could use `query-replace-regexp' a.k.a. C-M-%. > >> Nicolas mentions "org-footnote-normalize" which would turn old footnotes >> in new ones, but it does nothing in my case except adding a "* >> Footnotes" entry. > > You misunderstood. `org-footnote-normalize' used to turn every footnote > into [1], [2], ... whereas it now turns them into [fn:1], [fn:2],... IOW > it cannot be used to convert from old syntax to new one. > > Regards, -- Dr.Gerald Wildgruber eikones NFS Bildkritik NCCR Iconic Criticism Universität Basel Rheinsprung 11 CH-4051 Basel www.eikones.ch T. +41 (0)61 267 18 02 F. +41 (0)61 267 18 11 - Sent with mu4e
Re: [O] how to convert/normalize plain footnotes into [fn:] ones
Hello, Gerald Wildgruber writes: > I'm trying to convert older orgmode documents which have plain, > "[1]"-like footnotes into the newer "[fn:]" format. > > Can this be done automatically? You could use `query-replace-regexp' a.k.a. C-M-%. > Nicolas mentions "org-footnote-normalize" which would turn old footnotes > in new ones, but it does nothing in my case except adding a "* > Footnotes" entry. You misunderstood. `org-footnote-normalize' used to turn every footnote into [1], [2], ... whereas it now turns them into [fn:1], [fn:2],... IOW it cannot be used to convert from old syntax to new one. Regards, -- Nicolas Goaziou
Re: [O] [ANN] Add EXPORT_FILE_NAME keyword
Hello, Charles Millar writes: > Hi again, > > > On 12/21/2016 04:32 AM, Nicolas Goaziou wrote: >> Hello, >> >> Charles Millar writes: >> >> >>> However, I tried to export a subheading with, e.g. >>> #+EXPORT_FILE_NAME: /foo/baz, >>> and >>> the result is /foo/bar.pdf, not /foo/baz.pdf >> Where does "bar" come from? >> > I was not clear. I should have shown - > > * this heading > #+EXPORT_FILE_NAME: /foo/bar > > ** next heading > #+EXPORT_FILE_NAME: /foo/baz > > If i C-c C-e C-s l o "next heading" the document in that heading is > exported as /foo/bar.pdf, not /foo/baz.pdf This is expected, then. Only one keyword is supported. If you want to use a different file name per subtree, use the property instead. Regards, -- Nicolas Goaziou
Re: [O] Preventing Org from being installed by elpa
Karl Voit writes: > * Phillip Lord wrote: >> Karl Voit writes: >> >>> I got the tipp of creating «~/.emacs.d/elpa/org-3101/org-pkg.el» >>> with: >>> (define-package "org" "3101" "Dummy org mode package" 'nil) >> >> >> You could probably do something with package-pinned-packages also. > > Hm. > > I'm not an expert in package.el or package managers in general but > isn't "pinning" something different? I thought that pinning is > "install a package and prevent it from being updated". > > Whereas I want to avoid a package to be installed in the first > place. Pinning is to say "I want this package to come from this place". In this case, you want to say "I want this package to come from the file system". It seems a related issue. It's not going to happen unless someone codes it or reports it, though. Phil
[O] how to convert/normalize plain footnotes into [fn:] ones
Hi, I'm trying to convert older orgmode documents which have plain, "[1]"-like footnotes into the newer "[fn:]" format. Can this be done automatically? In https://lists.gnu.org/archive/html/emacs-orgmode/2015-12/msg00435.html Nicolas mentions "org-footnote-normalize" which would turn old footnotes in new ones, but it does nothing in my case except adding a "* Footnotes" entry. Thanks Gerald.
Re: [O] Preventing Org from being installed by elpa
* Phillip Lord wrote: > Karl Voit writes: > >> I got the tipp of creating «~/.emacs.d/elpa/org-3101/org-pkg.el» >> with: >> (define-package "org" "3101" "Dummy org mode package" 'nil) > > > You could probably do something with package-pinned-packages also. Hm. I'm not an expert in package.el or package managers in general but isn't "pinning" something different? I thought that pinning is "install a package and prevent it from being updated". Whereas I want to avoid a package to be installed in the first place. -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] Preventing Org from being installed by elpa
* Christian Wittern wrote:
> On 12/21/2016 05:07 AM, Karl Voit wrote:
>> I got the tipp of creating «~/.emacs.d/elpa/org-3101/org-pkg.el»
>> with:
>> (define-package "org" "3101" "Dummy org mode package" 'nil)
>>
>> And this simulates the fulfilled dependency so that my git version
>> of Org-mode is the only one installed (besides maybe the default one
>> from Emacs).
>
> Hmm, this sounds like what I want. However, when I try this, Emacs tells me:
>
> (file-error "Cannot open load file" "no such file or directory"
> "/home//.emacs.d/elpa/org-3101/org-autoloads")
>load("/home//.emacs.d/elpa/org-3101/org-autoloads" nil t)
>
> Is there a way to avoid this?
I'm sorry.
Usually, I do keep detailed notes on things I do. But when I created
this pseudo-package, I did not write down a detailed howto for my
future me.
But the input for this came from this mailing list. So please search
the archive and you might get the original instructions.
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] Preventing Org from being installed by elpa
Karl Voit writes: > * Eric Abrahamsen wrote: >> >> Actually, I have a third: the plain old Org package from the >> package repos, because I've installed other packages that require >> it. (Another gripe: why isn't the loading of a file containing >> (provide 'org) enough to tell the package manager not to install >> another one?) > > I got the tipp of creating «~/.emacs.d/elpa/org-3101/org-pkg.el» > with: > (define-package "org" "3101" "Dummy org mode package" 'nil) > > And this simulates the fulfilled dependency so that my git version > of Org-mode is the only one installed (besides maybe the default one > from Emacs). You could probably do something with package-pinned-packages also. This is probably something that package.el should support, so when not submit a bug report?
Re: [O] [ANN] Add EXPORT_FILE_NAME keyword
Hi again, On 12/21/2016 04:32 AM, Nicolas Goaziou wrote: Hello, Charles Millar writes: However, I tried to export a subheading with, e.g. #+EXPORT_FILE_NAME: /foo/baz, and the result is /foo/bar.pdf, not /foo/baz.pdf Where does "bar" come from? I was not clear. I should have shown - * this heading #+EXPORT_FILE_NAME: /foo/bar ** next heading #+EXPORT_FILE_NAME: /foo/baz If i C-c C-e C-s l o "next heading" the document in that heading is exported as /foo/bar.pdf, not /foo/baz.pdf Best, Charlie Millar
[O] sending an email to an orgmode file?
Hi im looking for a simple solution that will allow me to send an email from my mobile phone and habr that email either be appended to a txt(org) file or perhaps another solution to get my mobile on the go notes onto my laptop orgmode file. i tried orgzly and mobile org but i would prefer a simple solution as to send an email anyone have any thoughts on this? best Z
Re: [O] Preventing Org from being installed by elpa
On 12/21/2016 05:07 AM, Karl Voit wrote:
I got the tipp of creating «~/.emacs.d/elpa/org-3101/org-pkg.el»
with:
(define-package "org" "3101" "Dummy org mode package" 'nil)
And this simulates the fulfilled dependency so that my git version
of Org-mode is the only one installed (besides maybe the default one
from Emacs).
Hmm, this sounds like what I want. However, when I try this, Emacs tells me:
(file-error "Cannot open load file" "no such file or directory"
"/home//.emacs.d/elpa/org-3101/org-autoloads")
load("/home//.emacs.d/elpa/org-3101/org-autoloads" nil t)
Is there a way to avoid this?
All the best,
Christian
--
Christian Wittern, Kyoto
Re: [O] [ANN] Add EXPORT_FILE_NAME keyword
Hello, Charles Millar writes: > However, I tried to export a subheading with, e.g. > #+EXPORT_FILE_NAME: /foo/baz, > and > the result is /foo/bar.pdf, not /foo/baz.pdf Where does "bar" come from? > This is not the same result that using the PROPERTIES construct in > a subheading, which will export with the subheading :EXPORT_FILE_NAME: > /foo/baz, which does generate a short document named /foo/baz.pdf > > Should we be able to apply the new #+EXPORT_FILE_NAME: to a subheading > or does it work only for an entire buffer? As every keyword (i.e., #+KEYWORD syntax), it applies to the whole document. However export properties (i.e., :PROPERTY: syntax) override them. > Org mode version 9.0.2 (release_9.0.2-132-gc130b2 @ > /usr/local/share/emacs/site-lisp/org-mode/lisp/) > GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of > 2015-03-07 on trouble, modified by Debian > > 2. An editorial suggestion for the realted ORGNEWS item which > currently reads: > > Simiralry to ~:EXPORT_FILE_NAME:~ property, this keyword allow to > specify the name of the output file upon exporting the document. This > has also an effect on publishing. > > be changed along the following lines? > > Similar to ~:EPORT_FILE_NAME:~ property, this keyword allows the user > to specify the name of the output file upon exporting the document. > This also has an effect on publishing (or "This also effects > publishing." Of course. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Make fails on Git (c130b2e)
Thanks! William Denton writes: > I just pulled the source and ran make, and it failed here: > > Done (Total of 115 files compiled, 3 skipped) > make[2]: Leaving directory '/usr/local/src/org-mode/lisp' > make[1]: Leaving directory '/usr/local/src/org-mode/lisp' > make -C doc info > make[1]: Entering directory '/usr/local/src/org-mode/doc' > org-version: 9.0.2 (release_9.0.2-132-gc130b2) > makeinfo --no-split org.texi -o org > org.texi:10468: @item outside of table or list This was the culprit. A fix has been committed. Best regards Marco
