One problem I found after uninstalling my extension function is with
#+BEGIN/END blocks. For example, enable fontification for python,
elisp or whatever and write a long block like this:
#+BEGIN_XXX python
def xxx(x):
pass
def xxx(x):
pass
...
#+END_XXX python
Now scroll down to the
Oh, I see there have been some changes in
org-compute-latex-and-related-regexp in a previous commit. Now it
seems to be working at least for some simple examples. I'm working in
a long and complex beamer document so I will be able to more seriously
test this during the next few days. Also, I'm
Hi Nicolas, thank you for letting me know.
I've been giving it a try but it doesn't really fix the main problem
AFAICS (I've just redefined org-do-latex-and-related as in [1], maybe
I'm missing something). It's not surprising because I don't think you
can work around it without installing a
Hello,
Paul Lodder writes:
> If else blocks inside for loops in python cause IndentationError, it
> does accept the 'if' and the indented part below the 'if', but from
> 'else:' onwards the code is not evaluated anymore because of the
> 'unexpected indent'. I added an example code block in
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Hello,
Carlos Pita writes:
> So in order to get all this properly working:
>
> 1. Also ignore the limit in org-do-latex-and-related.
>
> 2. Install a region extension function so that multiline regions are
> properly identified at the start and after syntax breaking change
> (that is, at the
Allen Li writes:
> I have worked around this locally, but I hope we can revisit this later since
> it makes Org mode's user interface better.
I'm not totally convinced about that.
> Does it make sense for Org mode to keep a separate release branch so
> new features can be worked on while a
On Wed, Dec 19, 2018 at 6:11 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Allen Li writes:
>
> > Okay, thanks. I guess we can see how this works out with respect to users
> > like Brent using org-tags-match-list-sublevels or otherwise using
> > hierarchy.
>
> On second thought, this may not be a
Hello,
Allen Li writes:
> Okay, thanks. I guess we can see how this works out with respect to users
> like Brent using org-tags-match-list-sublevels or otherwise using
> hierarchy.
On second thought, this may not be a good idea, especially on master
branch, which is close from being released.
On Tue, Dec 18, 2018 at 3:18 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Allen Li writes:
>
> > Perhaps the stars should only be shown if
> > org-tags-match-list-sublevels is set to indented, so that the agenda
> > view matches
> > the column view with respect to showing hierarchy?
>
> I don't
Hello,
Allen Li writes:
> Perhaps the stars should only be shown if
> org-tags-match-list-sublevels is set to indented, so that the agenda
> view matches
> the column view with respect to showing hierarchy?
I don't think it makes sense since the aforementioned variable is not
related to
Hello,
Allen Li writes:
> On Wed, Dec 12, 2018 at 9:59 AM Nicolas Goaziou
> wrote:
>>
>> Could you give more context about the bug you're encountering? What does
>> mean "function correctly if a URL was not provided"? What is the use
>> case? What result did you expect, besides not
> Uwe Brauer writes:
> If your only problem with the original order was what you described before,
> don't change the order: just do
> (load-file "~/emacs/init/emacs_init.el")
> (setq custom-file "/home/oub/emacs/init/custom-init.el")
> (load-file
Uwe Brauer writes:
>> Uwe Brauer writes:
>
>> You are probably loading ox-beamer which adds it and then loading the
>> customized version which resets it. Try changing the order.
>
> The setting in my .emacs is:
> (load-file "~/emacs/init/emacs_init.el")
> (setq custom-file
> Uwe Brauer writes:
> You are probably loading ox-beamer which adds it and then loading the
> customized version which resets it. Try changing the order.
The setting in my .emacs is:
(load-file "~/emacs/init/emacs_init.el")
(setq custom-file "/home/oub/emacs/init/custom-init.el")
(load-file
Uwe Brauer writes:
> I have
> (require 'ox-beamer)
>
> In my org init file, which should via add-to-list, add beamer but somehow
> it does not.
>
> So when I call
>
> C-c C-e l b
>
> In a org file I obtain the message
>
> user-error: Unknown LaTeX class ‘beamer’
>
> Something is wrong here.
On Fri, Dec 14, 2018 at 6:36 AM Bernt Hansen wrote:
>
>
> In my custom agenda view for Projects I set
> (org-tags-match-list-sublevels 'indented)
Good to know, although I see that setting
org-tags-match-list-sublevels to anything other than t is
semi-obsolete.
However, we are talking mostly
Allen Li writes:
> On Thu, Dec 13, 2018 at 6:28 AM Bernt Hansen wrote:
>>
>> Allen Li writes:
>>
>> > On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou
>> > wrote:
>> >>
>> >> This is not satisfying, actually. If every item has a single asterisk,
>> >> you miss hierarchy between headlines in
Hello,
Allen Li writes:
> Apparently I'm missing something. How are you using hierarchy in an
> agenda view? Agenda views are flat, e.g.:
>
> tasks: TODO [#A] Some task
> tasks: TODO [#A] Some task
> tasks: TODO [#A] Some task
> tasks: TODO Some task
> tasks:
On Thu, Dec 13, 2018 at 6:28 AM Bernt Hansen wrote:
>
> Allen Li writes:
>
> > On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou
> > wrote:
> >>
> >> This is not satisfying, actually. If every item has a single asterisk,
> >> you miss hierarchy between headlines in the same tree.
> >
> > I
Hello,
Akater writes:
> I've been using Column View for quite some time without any
> issues. After today's update, C-c C-c on the BEGIN line of the dynamic
> block
>
> #+BEGIN: columnview :hlines 1 :id local :maxlevel 3
>
> [...]
>
> #+END:
>
> draws the table close to the very beginning of a
Allen Li writes:
> On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou
> wrote:
>>
>> This is not satisfying, actually. If every item has a single asterisk,
>> you miss hierarchy between headlines in the same tree.
>
> I don't know what you mean. Hierarchy is not displayed normally in
> agenda
I've been using Column View for quite some time without any
issues. After today's update, C-c C-c on the BEGIN line of the dynamic
block
#+BEGIN: columnview :hlines 1 :id local :maxlevel 3
[...]
#+END:
draws the table close to the very beginning of a buffer, starting at the
11th char, cells
On Wed, Dec 12, 2018 at 9:59 AM Nicolas Goaziou wrote:
>
> Could you give more context about the bug you're encountering? What does
> mean "function correctly if a URL was not provided"? What is the use
> case? What result did you expect, besides not encountering an error
> message?
The issue
On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou wrote:
>
> This is not satisfying, actually. If every item has a single asterisk,
> you miss hierarchy between headlines in the same tree.
I don't know what you mean. Hierarchy is not displayed normally in
agenda view anyway, I don't know why
Hello,
Allen Li writes:
> On Thu, Dec 6, 2018 at 6:35 AM Nicolas Goaziou wrote:
>> We could ignore the level when displaying ITEM in agenda column view. As
>> a consequence, every item would start with a single star, which is
>> shorter and still not confusing.
>
> Sounds good to me.
This is
Hello,
Allen Li writes:
> I didn't realize that org-protocol-capture is documented for URLs,
> since the concept of capturing through org-protocol is useful for
> non-web browser contexts.
>
> Anyway, I'm not interested in updating the documentation for
> org-protocol-capture at the moment, but
Hello,
Allen Li writes:
> I think this issue is medium/low priority and difficult to resolve. I
> have worked around it for my use case. However, I still think it is
> an issue since it's an edge case that users of org-map-entries will
> need to take into account.
This is not specific to
Attached patch
I didn't realize that org-protocol-capture is documented for URLs,
since the concept of capturing through org-protocol is useful for
non-web browser contexts.
Anyway, I'm not interested in updating the documentation for
org-protocol-capture at the moment, but even if
Using Org protocol capture without supplying a URL inserts a corrupt
entry into org-stored-links (nil ""). The nil causes a type error later
in org-insert-link.
(defun org-protocol-do-capture (info)
"Perform the actual capture based on INFO."
(let* ((temp-parts (org-protocol-parse-parameters
On Tue, Dec 11, 2018 at 8:27 AM Nicolas Goaziou wrote:
> > (((headline (:raw-value "stuff" :begin 17 :end 36 :pre-blank 0
> > :contents-begin 26 :contents-end 36 ...)) 17 35))
>
> `org-element-at-point' ignores narrowing.
Yes, but my issue is with the fact that the entry bounds reported by
Hello,
Allen Li writes:
> org-map-entries narrows the buffer to narrower than the given entry.
>
> 1. Run: cat > /tmp/tmp.org < * some headline
> ** stuff
> some text
> ** asdf asdf
> EOF
>
> 2. emacs -Q
> 3. M-g M-g 2 RET
> 4. M-: (org-map-entries (lambda () (list (org-element-at-point)
>
org-map-entries narrows the buffer to narrower than the given entry.
1. Run: cat > /tmp/tmp.org <
On Saturday, 8 Dec 2018 at 10:56, Nicolas Goaziou wrote:
> I'm nowhere close to being a LaTeX expert. If depending on xcolor is not
> too invasive, I'd rather do it than introduce yet another customization
> option.
>
> Maybe real LaTeX experts could chime in.
Whether expert or not, I can say
Hello,
Allen Li writes:
> There's an escaping bug in Org capture:
>
> 1. emacs -Q
> 2. Evaluate:
>
> (setq org-capture-templates
>'(("Z" "org-protocol capture" entry
> (file "/tmp/tmp")
> "* %?
> %(let ((x \"%:annotation\")) (if (string= x \"\") \"\" (concat x
> \"\\n\")))%i")))
Hello,
Carlos Pita writes:
>> Would you want to provide a patch for that?
>
> Yes, sure, just give me a few days since I'm quite busy right know.
>
> Are you ok with depending on xcolor by default or do you prefer a
> customization option?
I'm nowhere close to being a LaTeX expert. If
> Would you want to provide a patch for that?
Yes, sure, just give me a few days since I'm quite busy right know.
Are you ok with depending on xcolor by default or do you prefer a
customization option?
There's an escaping bug in Org capture:
1. emacs -Q
2. Evaluate:
(setq org-capture-templates
'(("Z" "org-protocol capture" entry
(file "/tmp/tmp")
"* %?
%(let ((x \"%:annotation\")) (if (string= x \"\") \"\" (concat x
\"\\n\")))%i")))
3. Evaluate (require 'org-protocol)
4.
On Thu, Dec 6, 2018 at 6:35 AM Nicolas Goaziou wrote:
> We could ignore the level when displaying ITEM in agenda column view. As
> a consequence, every item would start with a single star, which is
> shorter and still not confusing.
Sounds good to me.
>
> WDYT?
>
> Regards,
>
> --
> Nicolas
Hello,
Allen Li writes:
> On Tue, Dec 4, 2018 at 2:14 AM Allen Li wrote:
>>
>> Or did you mean ITEM omits the stars? That doesn't appear to be the
>> case as of 04641c4bbefc5f90e05fe4e846f4aeab15f1c262 on master
>> yesterday.
>
> So org-entry-properties does indeed return ITEM without the
Hello,
"Ulrich G. Wortmann" writes:
> no. I did not. How do checkout the "next" branch?
You need to install Org from git, as described in the manual. Then,
before calling "make", just use "git checkout next".
Regards,
--
Nicolas Goaziou
Hello,
Thank you for your quick patch.
Since I wasn’t able to solve it on my own, I’ll take a look at
your solution to understand what you did.
Have a great day.
Best,
Nicolas Goaziou writes:
Hello,
Leo Vivier writes:
Hello,
There seems to be a bad interaction between
>>> "Nicolas" == Nicolas Goaziou writes:
> Hello,
> Uwe Brauer writes:
>> When finishing a note and running C-c C-c I obtain an error which I
>> attach
>> ,
>> |
>> | Debugger entered--Lisp error: (error "Invalid version syntax: ‘N/A’
(must start with a number)")
Hello,
Uwe Brauer writes:
> When finishing a note and running C-c C-c I obtain an error which I
> attach
> ,
> |
> | Debugger entered--Lisp error: (error "Invalid version syntax: ‘N/A’ (must
> start with a number)")
> | signal(error ("Invalid version syntax: ‘N/A’ (must start with a
Hello,
Leo Vivier writes:
> Hello,
>
> There seems to be a bad interaction between ‘(org-resolve-clocks)’ and
> ‘org-clock-out-remove-zero-time-clocks’ set to t. Whilst the right
> tree is targeted by ‘(org-resolve-clocks)’ to delete the clock-line
> and clock-drawer, it adds a new clock-drawer
Hello,
Carlos Pita writes:
> As a more robust solution, I suggest to explicitly set the colors in the
> tex fragment for the preview instead of passing them as arguments to
> dvipng. This can be done easily:
>
> ...
> \usepackage{xcolor}
> ...
> \begin{document}
> \definecolor{bg}{rgb}{0,0,0}
Hello,
Tobias Zawada writes:
> AFAIK from general understanding of software development bugfixes
> should also be applied to the maintenance version of a program.
Org maint is totally frozen and bugfixes are applied to master instead.
It is inconvenient. Hopefully, it will change once Org 9.2
Dear Charles,
The problem is the update from master.
>From my understanding Master is more or less the development branch.
It is not what can be installed from org via package-install.
I believe that is the maint branch. But I can be mistaken.
Nevertheless, I had a look at the 9.14-Tag on
The quick and dirty option, if anyone wants it now:
(setq org-format-latex-header
(concat org-format-latex-header
"\\usepackage{xcolor}\n"
"\\definecolor{__bg__}{HTML}{1d1f21}\n"
"\\definecolor{__fg__}{HTML}{c5c8c6}\n"
Hi, I know this problem has been reported in the past ([1], [2]). The
second link provides a hint to a solution that I've developed
further. The underlying problem is (from dvipng man page):
-fg color_spec Choose foreground color for the images. This option will
be ignored if there is a
Hmmm.
I just updated from master using `make update2'.
I ran
/Applications/Emacs.app/Contents/MacOS/Emacs -q
which is morally equivalent to `emacs -q' on a linux box.
I had to customize `org-babel-load-languages' to add `shell'.
I copied your text to an org buffer did C-c ' to extract the
Dear Charles,
I installed orgmode 9.14 from org via ~package-install~.
The problem is still present there.
The messages from the evaluation of the last code block and the output of
~org-version~:
#+BEGIN_QUOTE
Wrote /temp/test1.org
executing Elisp code block (add3)...
(num (quote 5))
"8"
>> you go to Github
>> for the most up to date version it is GPLv3
>> https://github.com/stathissideris/ditaa/blob/master/LICENSE
>
> That file does not tell us how the code is licensed.
> It could be under GPL version 3 only, or GPL version
> 3-or-later.
> The proper way to use the GPL is
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> you go to Github
> for the most up to date version it is GPLv3
>
Dear Charles,
thanks for the quick test.
You wrote:
> I cannot reproduce this in 9.1.14
> C-c C-v C-i on each src block works as expected.
> org-babel-execute-buffer runs to successful completion.
I had a look at the orgmode master.
The problem has already been fixed in the master by
On 2018-12-04 4:10 a.m., Nicolas Goaziou wrote:
Michael Hoffman writes:
1. What exactly did you do?
- Execute:
(with-eval-after-load 'org
(add-hook 'org-shiftleft-final-hook 'windmove-left))
(org-agenda nil "a")
(split-window-horizontally)
- Type S-left
2. What did you expect to happen?
no. I did not. How do checkout the "next" branch?
thx
On Mon, 3 Dec 2018 at 12:15 Nicolas Goaziou wrote:
> Hello,
>
> "Ulrich G. Wortmann" writes:
>
> > I made a few more tweaks. The function now recognizes modifiers as to
> which
> > float environment to use, and where to place the float on
I cannot reproduce this in 9.1.14
C-c C-v C-i on each src block works as expected.
org-babel-execute-buffer runs to successful completion.
HTH,
Chuck
> On Dec 4, 2018, at 8:45 AM, Tobias Zawada wrote:
>
> I mostly cite here from https://emacs.stackexchange.com/q/41208/2370:
>
> The
I mostly cite here from https://emacs.stackexchange.com/q/41208/2370:
The following example causes an infinite recursion in
~org-babel-get-src-block-info~.
#+BEGIN_SRC org
,#+BEGIN_SRC org
,#+NAME: add3
,#+BEGIN_SRC elisp :var num=0
(+ 3 num)
,#+END_SRC
,* Use function drawer header arg
Hello,
Allen Li writes:
> Or did you mean ITEM omits the stars?
Yes, I did.
> That doesn't appear to be the case as of
> 04641c4bbefc5f90e05fe4e846f4aeab15f1c262 on master yesterday.
Actually, that should be the case since Org 9.0.
Do you have an ECM?
Regards,
--
Nicolas Goaziou
On Tue, Dec 4, 2018 at 2:14 AM Allen Li wrote:
>
> Or did you mean ITEM omits the stars? That doesn't appear to be the
> case as of 04641c4bbefc5f90e05fe4e846f4aeab15f1c262 on master
> yesterday.
So org-entry-properties does indeed return ITEM without the leading
stars, but the column view adds
On Mon, Dec 3, 2018 at 2:57 PM Nicolas Goaziou wrote:
>
> Hello,
>
> Allen Li writes:
>
> > (I used org-submit-bug-report, but this is a feature request.)
> >
> > It would be nice to have a special property like ITEM
> > without the leading stars, which is annoying in, e.g., the agenda column
>
> go to Github
> for the most up to date version it is GPLv3
> https://github.com/stathissideris/ditaa/blob/master/LICENSE
The official-looking site sends you to SourceForge. Git and Svn repo functions
are available there.
At the time, the git part of it was empty. Building the 131K jar
Hello,
Michael Hoffman writes:
> 1. What exactly did you do?
>
> - Execute:
> (with-eval-after-load 'org
> (add-hook 'org-shiftleft-final-hook 'windmove-left))
> (org-agenda nil "a")
> (split-window-horizontally)
>
> - Type S-left
>
> 2. What did you expect to happen?
>
> (windmove-left)
>
>
Hello,
Allen Li writes:
> (I used org-submit-bug-report, but this is a feature request.)
>
> It would be nice to have a special property like ITEM
> without the leading stars, which is annoying in, e.g., the agenda column
> view.
>
> I imagine that this will be easy to implement.
> There may be
1. What exactly did you do?
- Execute:
(with-eval-after-load 'org
(add-hook 'org-shiftleft-final-hook 'windmove-left))
(org-agenda nil "a")
(split-window-horizontally)
- Type S-left
2. What did you expect to happen?
(windmove-left)
3. What happened instead?
Received message "Command not
Cool, will do, thanks.
John.
On Mon, Dec 3, 2018 at 12:19 PM Nicolas Goaziou
wrote:
> Hello,
>
> John Lusk writes:
>
> > Trying to export the follow .org file to HTML:
> >
> > * Header 1
> >
> > #+BEGIN_SRC xml
> >
> >
> >
> >
> >
(I used org-submit-bug-report, but this is a feature request.)
It would be nice to have a special property like ITEM
without the leading stars, which is annoying in, e.g., the agenda column
view.
I imagine that this will be easy to implement.
There may be some UI implications (confusing in some
Hello,
John Lusk writes:
> Trying to export the follow .org file to HTML:
>
> * Header 1
>
> #+BEGIN_SRC xml
>
>
>
>
> #+END_SRC
>
> Results in the following error:
>
> cons: Args out of range:
Hello,
"Ulrich G. Wortmann" writes:
> I made a few more tweaks. The function now recognizes modifiers as to which
> float environment to use, and where to place the float on the page. E.g.
>
> #+ATTR_LATEX: :environment longtable
> #+ATTR_LATEX: :placment [t]
Thank you. However, I think the
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
I made a few more tweaks. The function now recognizes modifiers as to which
float environment to use, and where to place the float on the page. E.g.
#+ATTR_LATEX: :environment longtable
#+ATTR_LATEX: :placment [t]
I also had a quick look at the html export code to see whether I can add
the
Hello,
On Mon, Dec 3, 2018 at 5:28 AM Van L wrote:
> > As already pointed out by Nicolas Goaziou, org-mode also requires other
> > external stuff
>
> A data point.
>
> Ditaa requires a JRE as mentioned at
>
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-ditaa.html
>
> The
> As already pointed out by Nicolas Goaziou, org-mode also requires other
> external stuff
A data point.
Ditaa requires a JRE as mentioned at
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-ditaa.html
The litigious terms are
ditaa version 0.9, Copyright (C) 2004--2009
> the extension function becomes helpful again: this because the
> #+BEGIN/#+END matcher is incremental and eventually the region to
Well, on a closer inspection it's not that incremental, it's just
ignoring the limit...
(defun org-fontify-meta-lines-and-blocks-1 (limit)
(when
Hi all,
I've been adding some improvements to the region extension function
(pasted below) in order to better support nesting, but anyway I'm
convinced that the current approach to org-highlight-latex-and-related
== '(latex) is hopeless except for small fragments and should be
reworked or dropped
Hello,
There seems to be a bad interaction between ‘(org-resolve-clocks)’
and ‘org-clock-out-remove-zero-time-clocks’ set to t. Whilst the
right tree is targeted by ‘(org-resolve-clocks)’ to delete the
clock-line and clock-drawer, it adds a new clock-drawer in the
next tree rather than on
Hello,
"Ulrich G. Wortmann" writes:
>
> I know nothing about lisp, but I think I understand enough of the structure
> to propose the following changes:
>
> In my testfile, this preserves the current behavior if no #+CAPTION is
> present. However, if the #+CAPTION is not empty, the table will be
Hello,
Helge Stenström writes:
> I try to export org file to html, using C-c C-e h o
>
> I get: defconst: Symbol's value as variable is void: css-mode-syntax-table
This variable is not used in Org base. The problem may come from
a configuration of yours.
Regards,
--
Nicolas Goaziou
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
As a possible fix I implemented this
font-lock-extend-after-change-region-function:
(defun my-org-extend-region (beg end old-len)
(let ((begin-re "[\t ]*\\(#\\+BEGIN\\|begin{\\)")
(end-re "[\t ]*\\(#\\+END\\|end{\\)"))
(save-excursion
(goto-char beg)
Well, now I do have found a bug ;). It's related to the limit issue I
mentioned before. Indeed the problem with rehighlighting broken
environments and highlighting new environments also happens for basic
latex fontification when org-highlight-latex-and-related is set to
'(latex), it has nothing to
> (lambda (start end args)
> (org-src-font-lock-fontify-block "latex" start end
Or a safer version:
(lambda (start end prop face)
(when (eq face 'org-latex-and-related)
(org-src-font-lock-fontify-block "latex" start end)
Also note that
Hi Nicolas,
I know nothing about lisp, but I think I understand enough of the structure
to propose the following changes:
In my testfile, this preserves the current behavior if no #+CAPTION is
present. However, if the #+CAPTION is not empty, the table will be
exported as float with the proper
> all fontification is lost for the entire environment and never reapplied
The problem is with the limit argument passed by the font locking
framework to org-do-latex-and-related .
Once you natively fontified the environment this limit arg became non
nil and it's in general not enough to match
Hi Nicolas, thank you for your detailed answer!
To be honest I was wrapping my head around this until late tonight when it
all suddenly made sense and I more or less concluded the same you explained
about the role of each block and was going to say that you could indeed
dismiss this request.
Hello,
Carlos Pita writes:
> The behavior of
>
>(P) previews,
>(E) C-c ' editing and
>(F) native fontification
>
> is very inconsistent for latex:
>
> 1. $xxx$ and $$xxx$$ no (F) no (E) but (P)
I guess (E) could be added, we already do this for inline source code,
but no one
One last suggestion. I see the latex export backend takes any BEGIN_XXX and
outputs a \begin{XXX} environment. That would be almost what I was asking
for when XXX = equation or displaymath or whatever. Except that in that
case the inline preview wont work (for BEGIN_LATEX it was working just
Indeed it would be nice to have preview working for SRC blocks with lang =
latex too.
> > 1. #+BEGIN_LATEX could be changed to honor current fontification
> > setting
>
> This construct doesn't exist in Org.
Yes, I realized after posting, it was suggested in reddit but I was
unable to find any reference to it in the source code. Maybe it did
exist in the past since it's often
Hello,
Carlos Pita writes:
> So, to sum up:
>
> 1. #+BEGIN_LATEX could be changed to honor current fontification
> setting
This construct doesn't exist in Org.
> 2. #+BEGIN_EXPORT latex should be changed to allow inline preview
>
> I would say 2 is a bug.
It is not a bug. Why would it be
Ok, I got the "#+BEGIN_LATEX latex" idea from reddit, but exploring
the source code I realized that the right thing to do here is to
"#+BEGIN_EXPORT latex" which makes more sense and is less redundant.
Now the problem still exists that "#+BEGIN_EXPORT latex" won't do
inline preview.
So, to sum
Please, add the ability to fontify code inside
#+BEGIN_LATEX
...
#+END_LATEX
blocks. Embedded LaTeX doesn't get native fontification and SRC
blocks aren't the place to just get fancy colors (besides, latex inline
preview doesn't work for them). Currently there is this trick:
#+BEGIN_LATEX latex
Hello,
John Ciolfi writes:
> Hi
>
> I ran into a confusing error due to missing language for a code block. Given
> attached issue.org
> which contains:
>
> #+BEGIN_SRC
> if (a > 1) {
> }
> #+END_SRC
>
> if you convert to pdf using the attached issue_repro.el via:
>
>
Hi
I ran into a confusing error due to missing language for a code block. Given
attached issue.org
which contains:
#+BEGIN_SRC
if (a > 1) {
}
#+END_SRC
if you convert to pdf using the attached issue_repro.el via:
emacs --batch -L /path/to/org/install/emacs/site-lisp/org
Hello,
"Ulrich G. Wortmann" writes:
> I had a quick look at table.el
>
> It exports only a tabular command, not a table. Is there a way to make org
> wrap the
>
> \begin{tabular}
> \end{tabular}
>
> into a regular
>
> \begin{table}
> \end{table}
>
> This would be perfectly correct latex, and
I had a quick look at table.el
It exports only a tabular command, not a table. Is there a way to make org
wrap the
\begin{tabular}
\end{tabular}
into a regular
\begin{table}
\end{table}
This would be perfectly correct latex, and keep the export mechanism,
neatly separated
Cheers
Uli
On
Thanks for the feedback. Makes sense if the latex code in the tabular
environment is generated by table.el. I wonder however why the export to
ASCII produces a caption.
Cheers
Uli
On Sat, 24 Nov 2018 at 04:37 Nicolas Goaziou wrote:
> Hello,
>
> "Ulrich G. Wortmann" writes:
>
> > the
Dear Nicolas
> Nicolas Goaziou writes:
> Hello, Colin Baxter writes:
>> Hi,
>>> Gemini Lasswell writes:
>>
>> > In the "Requirements" section of ob-gnuplot.el's header
>> comment, > the link given for gnuplot-mode no longer works. The
>> same broken >
Hello,
Colin Baxter writes:
> Hi,
>> Gemini Lasswell writes:
>
> > In the "Requirements" section of ob-gnuplot.el's header comment,
> > the link given for gnuplot-mode no longer works. The same broken
> > link is also present in org-manual.org.
>
> > Since gnuplot-mode is
501 - 600 of 9192 matches
Mail list logo
