On 01/04/21 1:47 pm, Ramesh Nedunchezian wrote:
> (FWIW, the above snippet is from the README file of Emacs's official ELPA
> repo. cf. https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/README#n80)
While I was trying to convert the above `org' file to `info' I
observed the following:
1.
I'm forwarding this to the emacs-orgmode list as this is something org
maintainers probably need to see.
On Thu, 1 Apr 2021 at 15:43, Arthur Miller wrote:
>
> Is it me or is it a bug?
>
> When in org mode in an elisp block, this seems to confuse syntax
> checker:
>
> #+begin_src emacs-lisp
>
On 01/04/21 8:46 pm, Nicolas Goaziou wrote:
> Hello,
>
> Ramesh Nedunchezian writes:
>
>> When I export the following snippet to TexInfo format the export fails.
>>
>>
>> ** To add a package: (submission, submit)
>>
>> Adding a basic package is very simple. There are thorough
>
> This
Joost Kremers writes:
> On Fri, Apr 02 2021, Tim Cross wrote:
>> Getting backticks to font-lock correctly is relatively easy. Getting the
>> exporters to understand the new syntax is more of a challenge
>
> Don't the exporters work off of some intermediate representation, like Pandoc
> does? I
On Fri, Apr 02 2021, Tim Cross wrote:
> Getting backticks to font-lock correctly is relatively easy. Getting the
> exporters to understand the new syntax is more of a challenge
Don't the exporters work off of some intermediate representation, like Pandoc
does? I kinda thought that was what
Samuel Wales writes:
> n.b. everybody knows better in this thread, but the docstring of
> org-emphasis-alist seemed to me like `test` + reload would fontify.
Getting backticks to font-lock correctly is relatively easy. Getting the
exporters to understand the new syntax is more of a challenge
Hi!
I have noticed a few times that sorting tables with C-c ^ does not update
the formulas it contains. This has bitten me quite a bit, so it's good i
have backups :)
Here is a minimal example:
| A | B |
|+---|
|| 5 |
|| 4 |
| 8 | 3 |
| 6 | 2 |
|| 1 |
|+---|
| 14 | |
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.
n.b. everybody knows better in this thread, but the docstring of
org-emphasis-alist seemed to me like `test` + reload would fontify.
Maxim Nikulin writes:
> On 01/04/2021 02:24, Sébastien Miquel wrote:
>> George Mauer writes:
>>> is there a straightforward way to extend the org parser to do this?
>> For the cosmetic part, there's this piece of code from
>>
On 01/04/2021 02:24, Sébastien Miquel wrote:
George Mauer writes:
is there a straightforward way to extend the org parser to do this?
For the cosmetic part, there's this piece of code from
https://archive.casouri.cat/note/2020/better-looking-verbatim-markup-in-org-mode/index.html
Nicolas Goaziou writes:
> Switches predate Babel and its header arguments. Also, they are
> orthogonal to Babel. I don't know what a sound design would be here,
> tho.
Breaking backwards comparability is a tough call, but somehow I feel
that it would be appropriate here. A number of reasons
Hello,
Tom Gillespie writes:
> It is not possible to strip coderefs when tangling and also search for
> those coderefs using org-link-search. This is because org-link-search
> uses org-src-coderef-regexp which calls regexp-quote on the regexp
> string while org-babel-tangle-single-block does
Hello,
"Dauer, Michael" writes:
> I cannot expand a macro after underscore, as the following sample shows in
> detail:
>
> #+macro: xxx A
> * macro bug
> a _{{{xxx}}}
> a_{{{xxx}}}
The first pair of braces belongs to the sup/superscript syntax, as in
a_{foo}. IOW, you need a fourth pair of
Hello,
Ramesh Nedunchezian writes:
> When I export the following snippet to TexInfo format the export fails.
>
>
> ** To add a package: (submission, submit)
>
> Adding a basic package is very simple. There are thorough
This should now be fixed. Thank you.
Regards,
--
Nicolas Goaziou
Eric S Fraga writes:
> On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
>> And there is a final thing which (for me) seem to work better in
>> latex-mode compared to org. That's jumping to the ``next error'' with
>> some key stroke. That's important, LaTeX's own error output it quite
>>
Eric S Fraga writes:
> On Thursday, 1 Apr 2021 at 16:50, Timothy wrote:
>> I think in part this works for me because of a particular system I
>> have in place (that IMHO works *wonderfully* with Org) which I plan on
>> submitting patches to upstream (to Org) in the not-to-distant future.
>
>
Hi,
I recently read about the #+STARTUP parameter "hideblocks", but it doesn't seem
to have any effect in my set-up. All the blocks kept laughing straight in my
face. :-(
Any ideas about what could have gone wrong?
I use Org Mode 9.4.5 with Emacs 26.3, and I also tried closing the file and
On Thursday, 1 Apr 2021 at 21:23, Michael Gauland wrote:
> When I export, the result of the code block is "X is Hello", but when
> I use C-c C-c to evaluate the block in emacs, I get "X is"--the
> variable isn't defined.
Did you hit C-c C-c on the property line to update org's view of the
On Thursday, 1 Apr 2021 at 16:50, Timothy wrote:
> I think in part this works for me because of a particular system I
> have in place (that IMHO works *wonderfully* with Org) which I plan on
> submitting patches to upstream (to Org) in the not-to-distant future.
Interesting. Look forward to
On Thu, Apr 1, 2021 at 4:23 AM Michael Gauland wrote:
> When I export, the result of the code block is "X is Hello", but when I
> use C-c
> C-c to evaluate the block in emacs, I get "X is"--the variable isn't
> defined.
>
This works for me on org 9.4.
I had trouble getting a file-level
Michael,
i see "Hello" when i C-c C-c. i see this with "emacs -Q".
cheers, Greg
I vote against backticks, since I think we can learn to live with some
diversity. Running with the crowd, the latest fashion, would, in the end, leave
us with something like Word and Windows, that is, something which is
seductively easy to use the first two days, but a pain in the neck the rest
Eric S Fraga writes:
> On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
>> And there is a final thing which (for me) seem to work better in
>> latex-mode compared to org. That's jumping to the ``next error'' with
>> some key stroke. That's important, LaTeX's own error output it quite
Hello
I am using a Emacs with no custom config. Here is the version info
Emacs : GNU Emacs 28.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.24.24,
cairo version 1.16.0)
of 2021-03-20
Package: Org mode version 9.4.4 (release_9.4.4 @
/usr/local/share/emacs/28.0.50/lisp/org/)
When I
I'm confused about the use of the header-args property. It works as
expected when I
export a file, but not when I evaluate a code block manually. For example,
consider this file:
#+PROPERTY: header-args :var x="Hello" :exports both
#+begin_src shell
echo X is $x
#+end_src
When
Yes, this looks very promising. I'm looking forward to playing with it
when I have more time.
On 27/03/21 12:55 am, Juan Manuel Macías wrote:
> Hi Timothy,
>
> I really like your approach. And it is org/emacscentric! Minted has
> never quite convinced me, and gives me some trouble with certain
On Thursday, 1 Apr 2021 at 18:00, Tim Cross wrote:
> the only small bit of help I've found is org-lint, which has helped me
org-lint is very helpful indeed.
> Having said that, I find the most common cause of errors in the *.tex
> export is due to in-line Latex in my org file. I rarely run into
Eric S Fraga writes:
> On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
>> And there is a final thing which (for me) seem to work better in
>> latex-mode compared to org. That's jumping to the ``next error'' with
>> some key stroke. That's important, LaTeX's own error output it quite
On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
> And there is a final thing which (for me) seem to work better in
> latex-mode compared to org. That's jumping to the ``next error'' with
> some key stroke. That's important, LaTeX's own error output it quite
> poor, but jumping to error
Tim,
Your concerns are well founded. Essentially any cosmetic extension
to the org table syntax will be an unmaintainable, bug ridden
nightmare and would be an eternal burden on any attempts to formalize
correct behavior. I have a draft of a grammar for a significant
portion of Org syntax
On 2021-03-31, at 21:19, Timothy wrote:
> autofrettage writes:
>
>> Quick and Dirty: Bind key '`' to ~ in Emacs?
My first thought exactly. And I'd definitely use it - I need to use
Markdown more often than I'd like to (chat, wikis, (cloud-based) task
management system...).
>> (I guess it
32 matches
Mail list logo
