Well, at least there is a sane explanation. Ironically, I was also about to
complain about all my loose ">"s getting flagged. So they are related!
Would there be a way to make an exception for < and > inside of actual code
forms? Languages need them for "greater than" and "less than".
On Thu, May
Hi Jamie,
Thanks for the info and link.
Seems like I got too excited after Nicolas' reply and noticed exactly what
you pointed out.
I've now worked out that leaving the original buffer-wide properties in
place is OK.
But, as you suggested, I've added property drawer to the heading for the
Hello,
Eric Danan writes:
> Sure, here it is.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Marco Wahl writes:
> Using < and > as parenthesis in Org is questionable, I think.
In Org syntax, < and > often come in pair (timestamps, some links,
targets, radio targets). There is at least some interest in the current
behaviour.
> Also this behavior is not documented AFAICT.
I
I found a clarification on how mmm-mode works.
https://github.com/polymode/polymode/issues/187
> mmm-mode also allows having multiple major modes depending on cursor
position in the buffer. However, it does not fully replace major mode
locally. This mode is only taking care about keymap, menu,
> I see lens to be useful for the eev mode, too.
Never heard of eev, but judging by some demos, it's a way to execute elisp
commands interactively.
Something like stitching blocks of commands together, or the data to
operate on, or embedding a target such as a shell in the same buffer is the
>> Not sure what you mean. This is the problem, i.e., just this code
>>
>> #+begin_src emacs-lisp
>> (> 1 2)
>> #+end_src
>>
>> in an org file produces a parens mismatch, which, BTW, check-parens also
>> flags. Anywhere else (e.g., *scratch*) in Emacs this code produces no
>> mismatch.
> In an
Hi Lawrence,
Lawrence Bottorff writes:
> Not sure what you mean. This is the problem, i.e., just this code
>
> #+begin_src emacs-lisp
> (> 1 2)
> #+end_src
>
> in an org file produces a parens mismatch, which, BTW, check-parens also
> flags. Anywhere else (e.g., *scratch*) in Emacs this
Not sure what you mean. This is the problem, i.e., just this code
#+begin_src emacs-lisp
(> 1 2)
#+end_src
in an org file produces a parens mismatch, which, BTW, check-parens also
flags. Anywhere else (e.g., *scratch*) in Emacs this code produces no
mismatch.
On Thu, May 2, 2019 at 10:35 AM
I've been using Orgzly and have been pleased with it, but I find the tiny
checkboxes too small for my fumble fingers on my Pixel phone. I've not
found any way to expandify the view. Am I overlooking some existing
feature?
> On May 1, 2019, at 7:56 PM, Lawrence Bottorff wrote:
>
> Wondering if you have seen this over at emacs.stackexchange. Very puzzling
> why the parens mismatch in a babel emacs-lisp block, but not anywhere else in
> Emacs.
I don't know the details but this ECM might help:
#+begin_src
Mohamed Wael Khobalatte writes:
> Hi guys, I posted a question to the Emacs StackExchange
> (https://emacs.stackexchange.com/questions/50137/show-apple-calendar-events-in-org-mode),
> but I believe it's better asked here. Does anyone know how I can get
> my Apple calendar to show up in org-mode
Hi Andreas,
"Andreas Kiermeier" writes:
> The reason I did tried to do it this way was because it's simpler than
> having to say :export results for every source block.
> But, it a second call to
>
> #+PROPERTY: header-args+ :exports code
> Just before the #+INCLUDE gets everything working
1) If you need to insert columns in tables remember to add them from right
to left only. I had to repopulate an orgmode table after I modified
structure by adding a column to the right of already existing columns and
this involved file operations outside of orgmode. I might be able to make
a
Thanks for the quick reply.
Of course you are spot on, Nicolas.
Changing to
#+PROPERTY: header-args+ :exports code
Or
#+PROPERTY: header-args+ :exports both
Does indeed fix the problem.
The reason I did tried to do it this way was because it's simpler than
having to say :export results for
Hi Sharon,
The tex file is straight out of the export, and the second ”}” matches the
“\hypersetup{“ a few lines earlier.
Thanks,
Andreas
From: Sharon Kimble
Sent: Thursday, 2 May 2019 17:57
To: Andreas Kiermeier
Cc: emacs-orgmode@gnu.org
Subject: Re: [O] Problem with including file
Hello,
"Andreas Kiermeier" writes:
> --- begin test.org
>
> #+STARTUP: content indent hidestars fninline
>
> #+PROPERTY: header-args:R :session *R* :cache no
>
> #+PROPERTY: header-args+ :results output
>
> #+PROPERTY: header-args+ :exports results
Here, you prevent source blocks'
William Denton writes:
Thanks for replying Bill.
I did try shortening the column widths in the manner that you suggested but it
took so long for the table to be displayed, that I gave up, hence me wanting to
try some other possible solution.
Thanks
Sharon.
> On 1 May 2019, Sharon Kimble
"Andreas Kiermeier" writes:
Andreas.
Just a very quick glance at your problem, and in the tex output you've shown
there is a double closing bracket on 'pdflang={English}}'. If you correct that
then your output might be better, I don't know, but its certainly worth a try.
Thanks
Sharon.
> Hi,
Sure, here it is.
On 2019-04-27 18:51, Nicolas Goaziou wrote:
Hello,
Eric Danan writes:
As discussed previously,
https://lists.gnu.org/r/emacs-orgmode/2018-11/msg00038.html
here is a patch to make the list of commands in the org-attach
dispatcher customizable.
Applied, with small fixes.
> On 2 May 2019, at 03:05, Jorge P. de Morais Neto
> wrote:
>
> Jorge P. de Morais Neto writes:
>
>> Damon Permezel writes:
>>> [...]
>>> org-drill-entry: Symbol’s function definition is void:
>>> org-outline-overlay-data
>>>
>>> I was able to fix the problem by grepping for references
21 matches
Mail list logo
