Yes. In my case, I installed org-plus-contrib.
On Sat, Aug 8, 2015 at 1:09 PM, Kyle Meyer wrote:
> Peter Salazar wrote:
> > Yes, that worked! Thank you so much!
>
> Great. Just for future reference, these were the steps that worked?
>
> - C-u M-x org-reload
> - Uninstall and then reinstall fro
Good evening,
Emacs 24.4 and Org from Git.
Goal:
1) Visit every source block
2) If there is a NAME property
1) Then replace it's value with a UUID
3) If there is not an NAME property
1) Add an NAME property and give it a UUID.
`org-uuid' [provides] the functionality to create a UUID. It s
Good evening,
Emacs 24.4 and Org from Git.
Goal:
1) Visit every headline
2) If there is an ID property
1) Then replace it's value with a UUID
3) If there is not an ID property
1) Add an ID property and give it a UUID.
`org-uuid' [provides] the functionality to add the ID with a UUID.
[Th
Hello,
Rasmus writes:
> Can you try the attached patch? It seems to work on the example from the
> manual, but you likely have more straining examples at hand.
Thank you.
I pushed a similar patch in maint
(46f3f4c626d6dfe48c0101e3c994a929b542ba77).
Regards,
--
Nicolas Goaziou
On Sat, Aug 08, 2015 at 09:23:57PM +0200, Rasmus wrote:
> Eric S Fraga writes:
>
> > On Friday, 7 Aug 2015 at 16:23, Rasmus wrote:
> >
> > [...]
> >
> >> I guess there would also be no loss from actually inserting a "%" after
> >> \includegraphics[·]{·} in ox-latex.
> >
> > Except that then the
On 08/08/2015 05:18 PM, Rasmus wrote:
Hi Scott,
Scott Randby writes:
I'm beginning to wonder if upgrading to 8.3.1 is a mistake. I had no
trouble at all with 8.2.10, but many problems with 8.3.1. My latest
issue follows.
We appreciate your bug reports. If you have got the time, please keep
This should do it :
* Hello
** columns
:B_columns:
:PROPERTIES:
:BEAMER_env: columns
:BEAMER_opt: [c]
:END:
*** Column 1
:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.3
:END:
Colonne 1
*** Column 2
:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.7
:END:
Colonne 2
Fabrice
2
Hi Scott,
Scott Randby writes:
> I'm beginning to wonder if upgrading to 8.3.1 is a mistake. I had no
> trouble at all with 8.2.10, but many problems with 8.3.1. My latest
> issue follows.
We appreciate your bug reports. If you have got the time, please keep
testing Org 8.3 and let us know a
Hi,
[ deleted: discussion on beatification ]
>
> My initial reaction was to kill it as well. But I might feel like this a
> bit to often (I feel the same way about headline keywords like COMMENT).
There has been repeated 'bashing' of the COMMENT keyword lately on this
list. Let me just raise a
Eric S Fraga writes:
> On Friday, 7 Aug 2015 at 16:23, Rasmus wrote:
>
> [...]
>
>> I guess there would also be no loss from actually inserting a "%" after
>> \includegraphics[·]{·} in ox-latex.
>
> Except that then the suggestion I just made would not work and would in
> fact be quite confusing
Hi guys
It turns out i didnt have the org-plus-contrib packages installed (never
really used contrib stuff :)) and after installing that the problem seems
to be gone! :)
thx so much again and sorry for the trouble
best
Z
On Sat, Aug 8, 2015 at 8:15 PM, Kyle Meyer wrote:
> Xebar Saram wrot
On 08/08/2015 02:50 PM, Rasmus wrote:
Scott Randby writes:
Sorry for the noise, I figured out how to prevent the automatic
insertion of \hypersetup{...} by deleting the settings for
org-latex-hyperref-template
I'm curious to know what you are missing in org-latex-hyperref-template?
What do y
On 08/08/2015 02:52 PM, Rasmus wrote:
Scott Randby writes:
Until 8.3.1, I needed to use \% in an org document in order to get the
% symbol displayed when exporting to LaTeX. I just discovered that \%
messes up the exported document, and that using % only works. I've
also experimented with \$ a
Scott Randby writes:
> Until 8.3.1, I needed to use \% in an org document in order to get the
> % symbol displayed when exporting to LaTeX. I just discovered that \%
> messes up the exported document, and that using % only works. I've
> also experimented with \$ and $ and found the same behavior.
Scott Randby writes:
> Sorry for the noise, I figured out how to prevent the automatic
> insertion of \hypersetup{...} by deleting the settings for
> org-latex-hyperref-template
I'm curious to know what you are missing in org-latex-hyperref-template?
What do you need in order to use the provided
Sorry for the noise, I figured out how to prevent the automatic
insertion of \hypersetup{...} by deleting the settings for
org-latex-hyperref-template
Scott Randby
What happened to the variable org-latex-with-hyperref? It is missing in
8.3.1 and I need it. I have this set to nil so that I can can use the
following in my documents
#+LATEX_HEADER: \hypersetup{...}
How do I now prevent org from automatically inserting \hypersetup{...}
when exporting to LaT
On 7/3/14, Samuel Wales wrote:
> in maint, isearch very often puts ... at the top of the window. is
8.3 seems to do this a little more.
however, i have found that running scroll-lock-next-line after the
isearch repairs the buggy ellipsis.
is there a hook i can use to do so as a silly but effec
On 2015-08-08 at 14:19, Scott Randby wrote:
> Until 8.3.1, I needed to use \% in an org document in order to get the %
> symbol displayed when exporting to LaTeX. I just discovered that \%
> messes up the exported document, and that using % only works. I've also
> experimented with \$ and $ an
Until 8.3.1, I needed to use \% in an org document in order to get the %
symbol displayed when exporting to LaTeX. I just discovered that \%
messes up the exported document, and that using % only works. I've also
experimented with \$ and $ and found the same behavior.
I've looked through the 8
0 in outline
nil in agenda
On 8/8/15, Nicolas Goaziou wrote:
> What is the return value of (org-in-commented-heading-p) on your
> pseudo-commented headlines?
I don't have the impression you would need to hijack the export process. It
seems like you would need to call a function that gets data from some
source (e.g the org document) and then populates a template with that data,
and once that is done, call a regular export function. There are a number
of
I'm beginning to wonder if upgrading to 8.3.1 is a mistake. I had no
trouble at all with 8.2.10, but many problems with 8.3.1. My latest
issue follows.
When I update a table (using C-u C-c *, or C-u C-c C-c, or M-x
org-table-recalculate), the table doesn't update and I get the following
error
Xebar Saram wrote:
> Hi Kyle
>
> i tried uninstall and install with no success
What if you do 'C-u M-x org-reload' before this uninstall/reinstall?
--
Kyle
Peter Salazar wrote:
> Yes, that worked! Thank you so much!
Great. Just for future reference, these were the steps that worked?
- C-u M-x org-reload
- Uninstall and then reinstall from package-list-packages menu.
--
Kyle
Yes, that worked! Thank you so much!
On Sat, Aug 8, 2015 at 11:59 AM, Kyle Meyer wrote:
> Peter Salazar wrote:
> > Yes! That worked. What does this mean?
> >
> > I tried going to package-list-packages and uninstalling and reinstalling
> > org, but that didn't help. What's my next step?
> >
> >
I have an org beamer file with the following header since I generally
prefer top-alignment for frames:
#+latex_class_options: [aspectratio=169,t,presentation,bigger,fleqn]
I have some columns where I want vertically centered text, and am not
sure how to pass the option to \columns{} instead of an
Peter Salazar wrote:
> Yes! That worked. What does this mean?
>
> I tried going to package-list-packages and uninstalling and reinstalling
> org, but that didn't help. What's my next step?
>
> On Sat, Aug 8, 2015 at 9:27 AM, Nicolas Goaziou
> wrote:
>
>> Peter Salazar writes:
>>
>> > Sure, I'll
Yes! That worked. What does this mean?
I tried going to package-list-packages and uninstalling and reinstalling
org, but that didn't help. What's my next step?
On Sat, Aug 8, 2015 at 9:27 AM, Nicolas Goaziou
wrote:
> Peter Salazar writes:
>
> > Sure, I'll try that. I'm not quite sure how to fi
Unfortunately I now can't reproduce the problem, so I can't check if
my suggestion to byte compile ob-R.el works or not. When I did observe
the issue you describe that seemed to fix it, and at least one other
person confirmed that it worked for them as well.
Since it doesn't work for you I suggest
Peter Salazar writes:
> Sure, I'll try that. I'm not quite sure how to figure out what
> argument org-export-dispatch takes. Something like this? (org-reload
> (org-export-dispatch 'html))
I meant C-u M-x org-reload. Then regular export (e.g., C-c C-e l L).
Regards,
Hello,
Michael Welle writes:
> after the latest update from the package repository, tasks, that have the
> property style set to habit, did not show up as habits in the agenda
> anymore, i.e. the bar graph isn't shown. It turned out that the task
> description looks like follows:
>
> * TODO foo
Sure, I'll try that. I'm not quite sure how to figure out what
argument org-export-dispatch takes. Something like this? (org-reload
(org-export-dispatch 'html))
On Sat, Aug 8, 2015 at 3:29 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Peter Salazar writes:
>
> > I'm getting a strange error whenever
Alex Bennée writes:
> Nicolas Goaziou writes:
>
>> Alex Bennée writes:
>>
>>> Nicolas Goaziou writes:
FWIW, I export it without an error. Do you use a custom export
back-end?
>>>
>>> I'm using ox-reveal (for Reveal.js). I'm finding it hard to trigger an
>>> actual backtrace so mayb
On 08/04/2015 08:00 PM, Bastien Guerry wrote:
Hi Charles,
Charles Millar writes:
It has been a while since I searched the mailing list archives. Did I
miss an announcement or is the search engine broken?
Did you get any answer by Lars on this?
Thanks,
No.
I just tried the mail list arc
Nicolas Goaziou writes:
> Alex Bennée writes:
>
>> Nicolas Goaziou writes:
>>
>>> Hello,
>>>
>>> Alex Bennée writes:
>>>
I've been using org-mode as a source for my presentations but exporting
broke today following an ELPA update. It seems the line:
#+DATE: KVM Forum 2015
Alex Bennée writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> Alex Bennée writes:
>>
>>> I've been using org-mode as a source for my presentations but exporting
>>> broke today following an ELPA update. It seems the line:
>>>
>>> #+DATE: KVM Forum 2015
>>>
>>> Is no longer acceptable.
>>
>> F
Samuel Wales writes:
> ok, then i don't understand the code. (i thought that was how it
> determined whether it was a commented headline to skip.) (it's nil
> but commented headers show.)
My bad. I misread your question. It should be non-nil, indeed.
What is the return value of (org-in-commen
Correcting myself,
> I think it is as good as it can get. You probably have an awful lot of
> children to display.
This one may improve the situation:
(defun show-children (&optional level)
(save-excursion
(org-back-to-heading t)
(let* ((current-level (funcall outline-level))
In the past I've been pretty happy with the default Agenda formats for
display todo items and such. It used to bug me that you couldn't see the
lineage of the items in the todo list, but then I discovered
org-agenda-prefix-format, and the %b escape for breadcrumbs, and that
was good enough.
Now I'
Martin Leduc writes:
> Hi Bastien, thanks a lot for your response but I finally solved the
> issue by installing the package cm-super.
Thanks for confirming!
--
Bastien
Nicolas Goaziou writes:
> Hello,
>
> Alex Bennée writes:
>
>> I've been using org-mode as a source for my presentations but exporting
>> broke today following an ELPA update. It seems the line:
>>
>> #+DATE: KVM Forum 2015
>>
>> Is no longer acceptable.
>
> FWIW, I export it without an error. D
Samuel Wales writes:
> thanks, suvayu, how do i use this org element minor mode?
>
> i get hangs quite frequently, for example when sorting in the outline
> buffer.
The freeze is the consequence of a cache corruption, but it doesn't give
information about what caused that corruption (almost cert
Samuel Wales writes:
> i compiled it and tried it. it seems improved, to maybe 2.5s.
I think it is as good as it can get. You probably have an awful lot of
children to display.
Anyway, could you provide the same report using an un-compiled Org?
A report using ELP (elp-instrument-package and el
Hi Kyle
i tried uninstall and install with no success
best
Z
On Sat, Aug 8, 2015 at 10:28 AM, Kyle Meyer wrote:
> Hello,
>
> Xebar Saram wrote:
> > Hi
> >
> > just updated org today and now i get this error on startup:
> >
> >
> > Invalid function: org-babel-header-args-safe-fn
> >
> > is th
Kaushal wrote:
> That's odd. `setq-local` macro was added in emacs 24.3; it is in subr.el.
>
> (defmacro setq-local (var val)
> "Set variable VAR to value VAL in current buffer."
> ;; Can't use backquote here, it's too early in the bootstrap.
> (list 'set (list 'make-local-variable (list 'qu
Hello,
Peter Salazar wrote:
[...]
> The error says:
> (wrong-type-argument listp #("Test document" 0 13 (:parent (#1
> org-element-set-contents(#("Test document" 0 13 (:parent (#0
Is this the same issue as here?
http://permalink.gmane.org/gmane.emacs.orgmode/99535?
Things may have
Hello,
Xebar Saram wrote:
> Hi
>
> just updated org today and now i get this error on startup:
>
>
> Invalid function: org-babel-header-args-safe-fn
>
> is this related to the new release?
It may be related to an issue with compiling during the package
update[1]. Magit has also had problems wit
Hello,
Peter Salazar writes:
> I'm getting a strange error whenever I try to export an org file,
> and I'm not sure how to track down the cause. It seemed to start when I
> upgraded to org 8.3.1, but it's hard to tell because this is the first
> time I've exported anything in a week or so.
>
> T
Hello,
Alex Bennée writes:
> I've been using org-mode as a source for my presentations but exporting
> broke today following an ELPA update. It seems the line:
>
> #+DATE: KVM Forum 2015
>
> Is no longer acceptable.
FWIW, I export it without an error. Do you use a custom export back-end?
Rega
Peter Salazar writes:
> As I mentioned, I'm getting that same error, not just with #+DATE but also
> with #+TITLE, #+AUTHOR, etc. Any one of these is sufficient to break export
> for me.
Yeah further poking has shown they have all broken. I can't quite follow
the logic of the patch as to what t
51 matches
Mail list logo
