On 06/07/2024 16:59, András Simonyi wrote:
Well, what they typically want is using the original title case
despite a style not containing any explicit instruction that the title
field should be in title-case, which, according to the latest. 1.02
CSL standard (https://docs.citationstyles.org/en/s
Ihor Radchenko writes:
>> #+BEGIN_SRC emacs-lisp
>> (list (list 1 2) (list "/" "<>") 'hline (list 3 4) (list 5 6))
>> #+END_SRC
>>
>> Org Babel outputs
>> ...
>> with the second element of the list
>>
>> (list "/" "<>")
>>
>> swallowed, without a word.
>>
>> Why would Org Babel do this?
>
On Mon, 8 Jul 2024 at 12:57, Max Nikulin wrote:
> On 06/07/2024 16:59, András Simonyi wrote:
> If a style does not specify conversion or use "title" then result should
> be in title case. Title case is recommended for BibTeX databases. If you
> pass string in title case then conversion to title ca
Hi Ihor,
I think that it will make more sense to recognize Org markup in the >
BEAMER_SUBTITLE property value.
I agree, that would be a good idea. I tried to implement this in the
same way as with the frametitle:
,
| (let ((env (org-element-property :BEAMER_ENV headline)))
| (format "
When i comment something inside a source block but then decide to undo
the commenting, the cursor ends up on the very first line of the block.
Steps to reproduce:
1. emacs -Q
2. In a scratch buffer activate org-mode and paste this:
#+begin_src fundamental
aoisretnoairsetn
oarisetnoairse
aorsoiet
Greetings Torsten.
I use a transparent terminal over the PDF and then screenshot it!
This is, as you would expect, an ultralight and ultrafast solution.
In fact, I use mupdf to open the PDF, then open the venerable SC spreadsheet
calculator in a transparent terminal over it. Once ‘filled’, I
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.
---
This bug has been difficult to reproduce but several people have
encountered it, or symptoms of it. Most recently, there has been this
thread on Reddit:
https://www.reddit.com/r/emacs/comments/1drxsz6/tangled_0_code_blocks_from_filename_problem/
Unfortunately, replicating on emacs -Q has proven im
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.
---
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.
---
When I create a source block, pressing ENTER (RET) at the end of the
first line indents the cursor visually about 10 characters to the
right. If I press RET again to create a new line, it re-indents the
previously displaced line, but the new line is also incorrectly placed.
Steps to reproduce:
1.
Orm Finnendahl writes:
> I'm trying to grasp what you are proposing and have some questions to
> make sure I've understood (please correct me if I'm wrong):
(Just for some context, do not take my ideas as something you must
follow 100% accurately. I am largely brainstorming here. So, feel free
A quick correction: instead of "BibLaTex title fields" I should have written
"BibTeX or biblatex title fields".
best wishes,
András
On Mon, 8 Jul 2024 at 14:56, András Simonyi wrote:
>
> On Mon, 8 Jul 2024 at 12:57, Max Nikulin wrote:
> > On 06/07/2024 16:59, András Simonyi wrote:
> > If a styl
Orm Finnendahl writes:
> For the backend I'm planning to realize the following options
> (implemented as custom variables, which can be overwritten in the
> document):
>
> - org-html-multipage-export-directory
>
> The directory for the exported files (relative or absolute).
I am wondering abou
Hi,
Am Montag, den 08. Juli 2024 um 15:05:58 Uhr (+) schrieb Ihor Radchenko:
>
> We might also consider adding MULTIPAGE as an additional argument to the
> API function (just like BODY-ONLY, VISIBLE-ONLY, SUBTREEP that we
> already use), but that's probably an implementation idea we may or ma
Michael Mauger writes:
> This bug has been difficult to reproduce but several people have
> encountered it, or symptoms of it. Most recently, there has been this
> thread on Reddit:
> https://www.reddit.com/r/emacs/comments/1drxsz6/tangled_0_code_blocks_from_filename_problem/
>
> Unfortunately, r
Orm Finnendahl writes:
>> Yes, roughly like this. Ideally, we should simply modify
>> `org-export-as', but handling output file name may be a bit tricky -
>> it is somewhat awkwardly placed in the current ox.el API (see the
>> discussion in
>> https://list.orgmode.org/orgmode/25393.61240.135445.
Fernando Niño writes:
> Your bug report will be posted to the Org mailing list.
>
Thanks for reporting, but may you also share the full warning text?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about O
Li Yuxiao writes:
> When I tried to type table between \between \end blocks, for example
> \begin{pmatrix}
> \* table contents *\
> \end{pmatrix}
>
> The table contents are not recognized. For instance, I can't use Tab to
> go to next line. It turns out the result of org-at-table-p is nil. I
> de
On Monday, July 8th, 2024 at 11:45 AM, Ihor Radchenko
wrote:
> Michael Mauger michael.mau...@protonmail.com writes:
>
> > This bug has been difficult to reproduce but several people have
> > encountered it, or symptoms of it. Most recently, there has been this
> > thread on Reddit:
> > https://
noa writes:
> When generating a sitemap from org-publish with the anti-chronological...
>
> All the dates shown were the mtime of the files, rather than the dates i
> specified with the DATE keyword...
>
> I've tried running this with emacs -q and get the same issue, and also have
> updated to
Michael Mauger writes:
>> > (Note: the "..." in the last entry; sometimes it showed up as "\...".)
>>
>>
>> This is curious. May it be that you have non-default value of
>> `pp-default-function'?
>>
>
> I don't touch `pp-default-function' and I've confirmed that it is
> set to `pp-fill' in my
h...@heagren.com writes:
>> I think that it will make more sense to recognize Org markup in the >
>> BEAMER_SUBTITLE property value.
>
> I agree, that would be a good idea. I tried to implement this in the
> same way as with the frametitle ...:
You can use
(org-element-parse-secondary-string v
Am Montag, den 08. Juli 2024 um 15:29:47 Uhr (+) schrieb Ihor Radchenko:
> Orm Finnendahl writes:
>
> > For the backend I'm planning to realize the following options
> > (implemented as custom variables, which can be overwritten in the
> > document):
> >
> > - org-html-multipage-export-direct
Hi Ihor,
Am Montag, den 08. Juli 2024 um 15:56:48 Uhr (+) schrieb Ihor
Radchenko:
>
> Or we can make `org-export-as' retain INFO channel when returning the
> output. Then, we can make `org-export-to-file' make use of the INFO
> channel to decide the file name. This way, there will be no need
Any task which is a habit is listed in a special portion of the agenda for
consistency tracking. This is useful and convenient. However, this
apparently conflicts with scheduling the habit for a certain time. For
example, if I want to go for a run on Tuesday at 5pm, I would like to have
the option
26 matches
Mail list logo
