Hi,
Next step, @all, please help me filling up the list of codings vs.
languages. I currently am somehow confident of the following:
greek -> LGR
russian -> T2A
Thanks for contribs, /PA
On Mon, 12 Feb 2024 at 14:57, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > I'm
Ihor Radchenko writes:
> If your assignment has "GNU Emacs" in it, you are good to go.
Just found the scanned copy. It refers to "GNU EMACS (herein called
the Program)" in paragraph 1.(a). :-D
Also, in case it helps locate it, there is "RT:1798288" under my name on
the first page. And the
Ihor Radchenko writes:
> Juan Manuel Macías writes:
>
>>> When I try the patch with a simple file like
>>>
>>> Hello. 你好。
>>>
>>> I do not see any warnings or errors indicated.
>>
>> How weird... And don't they at least appear in the *Messages* buffer?
>> With your example, they appear to me
Martin Marshall writes:
> Ihor Radchenko writes:
>> I also see that you submitted a number of patches recently.
>> For now, your contribution size is fairly small, but if you plan to
>> contribute a lot more, please consider signing FSF copyright assignment.
>> See
Juan Manuel Macías writes:
>> When I try the patch with a simple file like
>>
>> Hello. 你好。
>>
>> I do not see any warnings or errors indicated.
>
> How weird... And don't they at least appear in the *Messages* buffer?
> With your example, they appear to me with pdfLaTeX, lualatex and XelaTeX
>
Ihor Radchenko writes:
> I also see that you submitted a number of patches recently.
> For now, your contribution size is fairly small, but if you plan to
> contribute a lot more, please consider signing FSF copyright assignment.
> See https://orgmode.org/worg/org-contribute.html#copyright
Martin Marshall writes:
> ... I just noticed that org-ctags breaks CUSTOM_ID property links
> in the same way. So I might submit a patch for that as well soon.
Improvements are always welcome!
I also see that you submitted a number of patches recently.
For now, your contribution size is
Juan Manuel Macías writes:
> Sorry, the previous patch was incomplete. The attached patch is correct.
When I try the patch with a simple file like
Hello. 你好。
I do not see any warnings or errors indicated.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
Sorry, the previous patch was incomplete. The attached patch is correct.
Best regards,
Juan Manuel
Juan Manuel Macías writes:
> Rationale for the attached patch: It seems that a common problem that
> users have with exporting to LaTeX is unicode characters that cannot be
> represented in
Ihor Radchenko writes:
> Applied, onto main, with amendments to the commit message.
> I added a TINYCHANGE cookie and linked to this thread.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=38dd88268
Thanks! I just noticed that org-ctags breaks CUSTOM_ID property links
in the
Rationale for the attached patch: It seems that a common problem that
users have with exporting to LaTeX is unicode characters that cannot be
represented in pdfLaTeX or LuaLaTeX/XelaTeX. In the Unicode TeX engines
the warning is insidious, since the missing character warning is not
preceded by a
Adam Porter writes:
> Since transient.el is part of Emacs now, these kinds of menus should
> probably be implemented with it.
IIUC, this is not a menu, but a reminder of key bindings that are usable
in that context. Other keybindings here are self-inserting keys, which
are equally useful, and
Stefan Kangas writes:
> Adam Porter writes:
>
>> Since transient.el is part of Emacs now, these kinds of menus should
>> probably be implemented with it.
>
> IIUC, this is not a menu, but a reminder of key bindings that are usable
> in that context. Other keybindings here are self-inserting
Ihor Radchenko writes:
> Stefan Kangas writes:
>
>> Adam Porter writes:
>>
>>> Since transient.el is part of Emacs now, these kinds of menus should
>>> probably be implemented with it.
>>
>> IIUC, this is not a menu, but a reminder of key bindings that are usable
>> in that context. Other
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.
Juan Manuel Macías writes:
> Many times I need to "save" an annotation point in the pdf-tools
> annotations buffer. So I defined a new link type and the function to
> store it. The link is stored with the structure:
> [[pdf-annot:/path/to/file.pdf::annotation-date][file-name.pdf (annot. on p.
Since transient.el is part of Emacs now, these kinds of menus should
probably be implemented with it.
Dear Ihor,
Ihor Radchenko writes:
>> My question: Is this the intended way to suppress bookmark creation?
>
> I think so.
Great!
> We first introduced `org-capture-bookmark' and only then added
> `org-bookmark-names-plist'. Maybe we should obsolete
> `org-capture-bookmark' to avoid confusion.
> The point of quick-help is to provide a persistent buffer
> with useful bindings, comparable to what Nano does OOTB.
> One critical difference between which-key and transient
> compared to quick-help, is that the latter has nothing
> to do with prefix maps, but (by default) just presents
>
Martin Marshall writes:
> Subject: [PATCH] org-ctags: Fix regexp to not break radio-target links
>
> * org-ctags.el (org-ctags-tag-regexp): Add left angle-bracket to
> excluded characters for tag text.
> ...
> This updates `org-ctags-tag-regexp' to avoid adding broken entries for
> radio targets
Pedro Andres Aranda Gutierrez writes:
> I'm trying to put together all pieces for this before I actually write code.
>
> After looking at the current state, I would be lenient to include an
> additional optional property to `org-latex-language-alist' I would directly
> call `:fontenc'.
>
>
Ihor Radchenko writes:
>> Is there a way to retain the alignment information when re-exporting to
>> Org? - either a function or some setting somewhere
Alignment markers and other special table rows are now exported by
default in ox-org.
Ihor Radchenko writes:
>> But I do think it would be helpful if the "order" while ex-
>> porting would be documented in a meaningful way.
Details of the export flow have been added to the manual.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=46cf76259
Ihor Radchenko writes:
> ... See the attached.
> I added reference to the manual in `org-export-as' docstring and made it
> explicit that the manual section is related to `org-export-as' by adding
> #+findex entry.
Applied, onto main.
Ihor Radchenko writes:
>> 2) Is there a reason why the Beamer theme options are exported after
>> other LaTeX packages? Wouldn't it be better to export the Beamer theme
>> options before loading additional packages? The reason for that being
>> that the theme sets defaults, which can then
Ilya Chernyshov writes:
> Hi, just wanted the code to be more elisp style guide compliant, so here's
> a patch that adds spaces before opening parentheses.
Sorry, but we do not accept whitespace-only commits because they may
create problems when searching git history. See
Hi,
The attached patch allows to use org-bibtex-yank to
populate an existing item instead of creating a new one,
aligning its behavior with org-bibtex-create.
BR,
Martin Kampas
>From 96af3ef46bb056e58206af77d3d37c5af2e43d7f Mon Sep 17 00:00:00 2001
From: Martin Kampas
Date: Mon, 12 Feb 2024
Ihor Radchenko writes:
> I am leaning towards removing the mention from the manual, but would
> like to hear from others.
>
> Is anyone using org-fast-tag-selection-include-todo? Does anyone think
> that documenting it properly would be useful?
No replies within one month, so I am going ahead
Hi, just wanted the code to be more elisp style guide compliant, so here's
a patch that adds spaces before opening parentheses.
>From 0d9b7ce6d5e83d7758566dab6a17642fdf4b9b73 Mon Sep 17 00:00:00 2001
From: Ilya Chernyshov
Date: Mon, 12 Feb 2024 18:33:29 +0600
Subject: [PATCH] Fix formatting
*
Juan Manuel Macías writes:
> Loris Bennett writes:
>
>> The blocks of the histogram are present in the PDF, but are white, like
>> the background of the slides. I can see this by marking them with the
>> mouse.
>>
>> Does anyone know what I need to do to make the full block character
>> visible
Max Nikulin writes:
> On 04/06/2022 20:42, Ihor Radchenko wrote:
>>
>> It appears that using mailcap is giving us more trouble than benefits.
>> I am not sure about the situation on Windows and Mac though.
>>
>> Should we change the default file handlers to Emacs globally (unless
>> user
Hi,
I have a command line tool which generates an ASCII histogram. I would
like to include the output in a PDF Beamer presentation.
Currently I am using an 'example' block, thus:
#+begin_example
...
-
CPU Efficiency (%)
-
0.00 - 10.00 [
32 matches
Mail list logo
