Dear all,
Another OrgMeetup will be scheduled on the second Wednesday of December,
next week.
[ Last month was skipped due to EmacsConf and my ]
[ https://emacsconf.org/2023/talks/gc/]
Previous meetup notes:
https://list.orgmode.org/orgmode/87edhtfpal.fsf@localhost/
URL: https://
Ihor Radchenko writes:
> This is because the default value of `org-babel-default-header-args'
> already contains (:tangle . "no").
...
> As internal implementation detail, Org babel prefers the _last_ header
> arg value in the above list. Which is why you end up seeing what you are
> seeing.
>
>
Liu Hui writes:
>> Makes sense.
>> I think we may drop a note about this new feature in ORG-NEWS.
>
> Thanks, I have added it in the attached patch.
> ...
> +When editing a Python src block, the editing buffer is now associated
> +with the Python shell specified by the src block's ~:session~ head
Kyle Meyer writes:
>> Aside: It appears to be only partially documented in
>> https://orgmode.org/worg/org-maintenance.html#emacs-sync. In particular,
>> the last two lines.
>
> I'm happy to clarify or add to those docs. I didn't write them, but I
> did go through them somewhat recently to bette
Hi Leo,
On Tuesday, 5 Dec 2023 at 20:18, Leo Butler wrote:
> I think it should be easy to provide this for a few data types (matrix,
> string, maybe list), but I think the conversion from a Lisp sexp to an
> ELisp sexp will need a lot of assumptions. E.g. how to convert the
> Maxima list:
>
> [[a
Colin Baxter writes:
>> Ihor Radchenko writes:
>
> > Colin Baxter writes:
> >> https://orgmode.org/worg/org-tutorials/org-google-sync.html
> >> suggests using the command line program 'googlecl'. That program
> >> appears to have been dead for several years, at least accordi
William Denton writes:
>> ASCII export:
>
> Huh! I never tried ASCII export. I see HTML works, too.
>
> Try LaTeX or ODT. My apologies, I should have specified that. It should
> throw
> an error that starts like this:
>
> Debugger entered--Lisp error: (wrong-type-argument char-or-string-p (
Hi,
I would like to export all =verbatim= marked text as small caps \textsc{} in
org-latex export. Code markup should be kept as verbatim, though.
I wasn't able to find any help in the org documentation, nor in the ob
customization in Emacs. I would appreciate it, If anybody has an idea how I
Alexander Gogl writes:
> I would like to export all =verbatim= marked text as small caps \textsc{} in
> org-latex export. Code markup should be kept as verbatim, though.
>
> I wasn't able to find any help in the org documentation, nor in the ob
> customization in Emacs. I would appreciate it, I
Ihor Radchenko writes:
> Alexander Gogl writes:
>
>> I would like to export all =verbatim= marked text as small caps \textsc{} in
>> org-latex export. Code markup should be kept as verbatim, though.
Or even easier: customize `org-latex-text-markup-alist'.
--
Ihor Radchenko // yantar92,
Org m
Thanks for digging into this, Ihor. It exports now, but I'm afraid it's
doing too much capitaliztion.
A name like "van Dongen" should become "Van Dongen" when cited with a caps
variant, for example [cite/a/c:@friends]. This is turning it into "VAN DONGEN",
upcasing the whole string when it s
On Monday, December 4, 2023 1:06:37 PM UTC you wrote:
> chris writes:
> > The code below is working fine as long as I stay in `org-mode`. But it
> > shows its limitations when I do `M-x org-publish-all`, at which time,
> > instead of having the text with style verbatim, I get the text within
> > b
Ihor Radchenko 于2023年12月6日周三 21:20写道：
>
> Liu Hui writes:
>
> >> Makes sense.
> >> I think we may drop a note about this new feature in ORG-NEWS.
> >
> > Thanks, I have added it in the attached patch.
> > ...
> > +When editing a Python src block, the editing buffer is now associated
> > +with the
Ihor Radchenko writes:
> I think that a reference to
> https://git.kyleam.com/orgmode-backport-notes/tree/orgmode-backports.org#n2
> might be helpful.
Okay, I'll make a note to add one.
> Maybe we should even have that file in the main repo as a part of
> emacs-sync branch?
I prefer not to. I
Ihor Radchenko writes:
> David Masterson writes:
>
>>> To prevent fill-region from concatenating the auto-generated text in the
>>> first line and the user input in the following lines.
>>
>> Ah. Is that mentioned somewhere in the Org manual? I don't mean the
>> details of fill-region, but a l
Ihor Radchenko writes:
> David Masterson writes:
>
>> I keep a number of Org files in buffers when I'm working on Org stuff. I
>> try to keep them folded so that I get the overview when I switch to the
>> buffer. I have found that, when I org-publish the project with these Org
>> files, any Org
16 matches
Mail list logo
