Re: [O] "Capture"-like browser plugin?
Hello Daniele, On 2015-07-23 16:47, Daniele Pizzolli writes: > if you use firefox, see: > > https://addons.mozilla.org/it/firefox/addon/org-mode-capture/ > > The latest version convert html links to org-links (disclaimer: it is my > little contribution). This is great! If I may suggest an addition to it: being able to specify how one calls emacs. Indeed, my emacsclient is a symbolic link to the real one, which may change as I update it, but the preference interface of the addon only gives me the target of the symbolic link. I have also a small issue with org-protocol: it creates a new frame (which is great) but does not raise it, and it displays two windows: the capture one and an unrelated one. I have some code to avoid this when I call org-capture from my system: #+begin_src emacs-lisp (defun make-orgcapture-frame () "Create a new frame and run org-capture." (interactive) (make-frame '((name . "remember") (width . 80) (height . 16) (top . 400) (left . 300) (font . "-*-Consolas-normal-normal-normal-*-13-*-*-*-m-0-iso10646-1") )) (select-frame-by-name "remember") (delete-other-windows) (flet ((switch-to-buffer-other-window (buf) (switch-to-buffer buf))) (org-capture nil "c"))) #+end_src but I don’t know how to integrate this with org-protocol. Is there a way to change its call to org-capture without having to rewrite the `org-protocol-do-capture' function? Thanks! Alan -- OpenPGP Key ID : 040D0A3B4ED2E5C7 Last week athmospheric CO₂ average (Updated July 19, 2015, Mauna Loa Obs.): 401.39 ppm signature.asc Description: PGP signature
[O] Offline until August 2nd
Hello, FWIW, I'll be offline for a week. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] export to html stuck in loop scanning for org IDs
Hi Bruce, Bruce Gilstrap writes: > This happens consistently with one file that I successfully exported last > Friday under 8.2.10 but does not happen at all with some other files. So > far, I have been unable to isolate exactly what it is about this file that > causes the export to get stuck in this loop. I can do the legwork to track > it down if someone more knowledgeable about the exporter can point me in > the right direction. It seems obvious that it has something to do with IDs, > but the files that still export properly contain IDs, too, so the issue > isn't as simple as the existence of IDs in the file. Would it be possible to bisect your file to find the offending part? Otherwise you could try to hot-patch org-id-update-id-locations in org-id.el. For instance, try to change the last (if ...) to: (if (> ndup 0) (message "WARNING: %d duplicate IDs found, check *Messages* buffer" ndup) (progn (message "%d unique files scanned for IDs" (length org-id-files)) (message (mapconcat (lambda (x) (format "%s" x)) org-id-files "\n" To see which files it is scanning. Maybe that will give a clue as to where the problem is. Do you use #+INCLUDE? Rasmus -- Er du tosset for noge' lårt!
Re: [O] org-version N/A when using git subtree
Excellent idea. I'll try that when I meddle with it next. Thank you. Johan 2015-07-22 03:00 skrev Grant Rettke: Generate autoloads with out make? http://orgmode.org/worg/org-hacks.html Grant Rettke -- g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates “All creativity is an extended form of a joke.” --Kay ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Mon, Jun 22, 2015 at 11:15 AM, Johan Sandblom wrote: This is off topic, or at least the first paragraph is, but I don't know where else to ask ... I maintain a private git repo where the org-mode git repo is included. I use it on several machines, both windows and linux, and also on a stick which I can use on the terribly restricted and firewalled computers at work (which curiously allow me to run emacs from the stick!). I used to include org-mode as a "fake submodule" (http://debuggable.com/posts/git-fake-submodules:4b563ee4-f3cc-4061-967e-0e48cbdd56cb) but wanted to learn more about git so I changed to a real submodule. This was annoying because then I could no longer just pull from the repo to the stick and have my new org-mode with me, I needed to update the submodule on the stick as well, which was more work than before. I then changed to using a git subtree for org-mode and lots of other bits and pieces that I wanted handy, even behind the firewall at work. This works great except for one thing: org-version is set to N/A (on topic again I hope). As far as I have been able to gather with my non-existent developer skills the org-version stems from mk/default.mk and so could be adjusted in local.mk, but I am unable to figure out where I should get it from, and how to adjust it. Can you enlighten me? Johan -- Johan Sandblom, MD PhD m +46735521477 What is wanted is not the will to believe, but the will to find out, which is the exact opposite --Bertrand Russell -- Johan Sandblom, MD PhD m +46735521477 What is wanted is not the will to believe, but the will to find out, which is the exact opposite --Bertrand Russell
[O] Change color for two words in LaTeX export using cologr package?
Hi
In an org document, I want to change the text colour of two words
{\color{red} red line } to red in a sentence and the rest should be
normal colour.
I am missing something, as this changes the text colour for the rest of
the sentence into red. How can I only change the colour of the two
words?
Thanks,
Rainer
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D):+49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
PGP: 0x0F52F982
signature.asc
Description: PGP signature
Re: [O] Change color for two words in LaTeX export using cologr package?
On Friday, 24 Jul 2015 at 15:07, Rainer M Krug wrote:
> Hi
>
> In an org document, I want to change the text colour of two words
> {\color{red} red line } to red in a sentence and the rest should be
> normal colour.
>
> I am missing something, as this changes the text colour for the rest of
> the sentence into red. How can I only change the colour of the two
> words?
I usually do this type of thing as follows:
#+latex: {\color{red}
red line
#+latex: }
which allows for org-isms in the text. Alternatively, you could do:
... @@latex:{\color{red} red line}@@
if you don't need to use org syntax within the {}.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1293-g985420
Re: [O] Change color for two words in LaTeX export using cologr package?
Eric S Fraga writes:
> On Friday, 24 Jul 2015 at 15:07, Rainer M Krug wrote:
>> Hi
>>
>> In an org document, I want to change the text colour of two words
>> {\color{red} red line } to red in a sentence and the rest should be
>> normal colour.
>>
>> I am missing something, as this changes the text colour for the rest of
>> the sentence into red. How can I only change the colour of the two
>> words?
>
> I usually do this type of thing as follows:
>
> #+latex: {\color{red}
> red line
> #+latex: }
>
> which allows for org-isms in the text. Alternatively, you could do:
>
> ... @@latex:{\color{red} red line}@@
>
> if you don't need to use org syntax within the {}.
Thanks - I will try it out on Monday. But it looks good.
Thanks,
Rainer
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D):+49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
PGP: 0x0F52F982
signature.asc
Description: PGP signature
[O] Shifting only past timestamps
Hello, I like to be reminded to check my post on Mondays and Thursdays, every week. When I've done it on Monday, I mark it 'DONE' so that I can stop org-mode reminding me until Thursday. Here's how I used to achieve this: *** URGENT [#A] Check post :important: DEADLINE: <2015-07-27 Mon +1w -0d> DEADLINE: <2015-07-30 Thu +1w -0d> In org-mode 8.2.10, if I mark 'Check post' as 'DONE', both timestamps will be moved forward one week. This is no good, as I need to be reminded to check my post on Thursday. I think I got the desired behaviour in the last version of org-mode I used, which I think was this 7.8.11 from this package: https://packages.debian.org/wheezy/org-mode How can I make org-mode shift only the timestamps from the past? Thanks in advance, Ed
Re: [O] export to html stuck in loop scanning for org IDs
Rasmus, I had started down the path of bisecting the file, but wasn't having much luck isolating the problem, so I posted the question. I had some time to get back to it this afternoon, and I eventually tracked this down. It had to do with a missing ID rather than a duplicate one. The file contained a link to an ID that no longer existed in the file (or in any other org files), but it wasn't listed in the *Messages* buffer and export kept searching through all my org files over and over until I pressed C-g. When I removed that link, I still had some other problems in the file with text links, i.e. [[target]], that didn't have a matching target, i.e., <>, but now these were identified in the *Messages* buffer (one per export attempt until I found them all). Once all of those were fixed, the export ran successfully. I do use #+INCLUDE, but that is not the problem here. Thanks, Bruce On Fri, Jul 24, 2015 at 4:38 AM, Rasmus wrote: > Hi Bruce, > > Bruce Gilstrap writes: > > > This happens consistently with one file that I successfully exported last > > Friday under 8.2.10 but does not happen at all with some other files. So > > far, I have been unable to isolate exactly what it is about this file > that > > causes the export to get stuck in this loop. I can do the legwork to > track > > it down if someone more knowledgeable about the exporter can point me in > > the right direction. It seems obvious that it has something to do with > IDs, > > but the files that still export properly contain IDs, too, so the issue > > isn't as simple as the existence of IDs in the file. > > Would it be possible to bisect your file to find the offending part? > Otherwise you could try to hot-patch org-id-update-id-locations in > org-id.el. For instance, try to change the last (if ...) to: > > (if (> ndup 0) > (message "WARNING: %d duplicate IDs found, check *Messages* > buffer" ndup) > (progn (message "%d unique files scanned for IDs" (length > org-id-files)) >(message (mapconcat (lambda (x) (format "%s" x)) > org-id-files "\n" > > To see which files it is scanning. Maybe that will give a clue as to > where the problem is. > > Do you use #+INCLUDE? > > Rasmus > > -- > Er du tosset for noge' lårt! > > >
