Am Mittwoch, dem 22.12.2021 um 10:37 -0800 schrieb Jason Ross:
>
> Thank you for bringing this up. I'd like to discuss this a bit with
> you
> before implementing such a feature.
>
> I'm not sure how an implementation of this would look to the end
> user.
> ConTeXt has the following system:
> htt
> On Dec 22, 2021, at 2:16 PM, Yasushi SHOJI wrote:
>
> Hi,
>
> On Thu, Dec 23, 2021 at 3:22 AM Berry, Charles
> wrote:
>>> On Dec 22, 2021, at 8:07 AM, Yasushi SHOJI wrote:
>>> On Thu, Dec 23, 2021 at 12:52 AM Yasushi SHOJI
>>> wrote:
Then, why don't I have :file in the info?
>>>
Daniel Kraus writes:
> I filled out the copyright assignment and waiting for them.
> I'll mail again when it's done.
Just want to mention that I finally received my signed of the copyright
agreement.
so there is no blocker from this site in case it doesn't count as tinychange.
Thanks,
Dani
Hi,
On Thu, Dec 23, 2021 at 3:22 AM Berry, Charles wrote:
> > On Dec 22, 2021, at 8:07 AM, Yasushi SHOJI wrote:
> > On Thu, Dec 23, 2021 at 12:52 AM Yasushi SHOJI
> > wrote:
> >> Then, why don't I have :file in the info?
> >
> > The :exports must be "file" to have the file name in the info. I
>
> May you provide a step-by-step reproducer starting from emacs -Q?
>
> Best,
>
> Ihor
Thanks Ihor,
It is neither an emacs nor an org-mode issue, but it concerns the way of
calling a php scritpt from an html file, and it is not easy, at least for me.
I admit that my email is therefore irrel
On 12/22/21 3:24 AM, juh wrote:
In the meantime I debugged my context styles and discovered that ox-
context starts with section not with chapters. My styles are always
book styles starting at chapter level. *feeling a little dumb*
I browsed through the code and found no hint for a book-like pre
> On Dec 22, 2021, at 8:07 AM, Yasushi SHOJI wrote:
>
> On Thu, Dec 23, 2021 at 12:52 AM Yasushi SHOJI
> wrote:
>> Then, why don't I have :file in the info?
>
> The :exports must be "file" to have the file name in the info. I used
> to have "code" because
> I wanted to export code with the
Max Nikulin writes:
>> Let me know if I'm missing anything so this can be merged. It is correct to
>> report errors this way, right?
>
>> + (when-let* ((err (geiser-eval--retort-error ret)))
>
> Doesn't (require 'subr-x) should be added to the file?
Hmm. You are right. I thought th
On Wednesday, 22 December 2021 11.54.33 -03 Ihor Radchenko wrote:
> Felipe Lema writes:
>
> > I started using guile with Org Babel and I was a little confused that
> > errors weren't being reported. The attached patch will report the error the
> > same way as python evaluation does.
>
> The pa
On 22/12/2021 02:58, Felipe Lema wrote:
Let me know if I'm missing anything so this can be merged. It is correct to
report errors this way, right?
+ (when-let* ((err (geiser-eval--retort-error ret)))
Doesn't (require 'subr-x) should be added to the file?
On Thu, Dec 23, 2021 at 12:52 AM Yasushi SHOJI wrote:
> Then, why don't I have :file in the info?
The :exports must be "file" to have the file name in the info. I used
to have "code" because
I wanted to export code with the file name as an attribute.
I think I can work on it.
Thanks Ihor for y
Robert Nikander writes:
> Also the bug I reported is back.
>
> Maybe I’ll just stick with the builtin org package 9.4.4.
Actually, I missed that you are on ELPA version. Apparently I forgot to
fix the problem on stable Org version (which is what you get from ELPA).
I pushed the fix now. It s
Hi Ihor,
On Wed, Dec 22, 2021 at 11:32 PM Ihor Radchenko wrote:
> Yasushi SHOJI writes:
> > I'm writing an exporter and I'd like to get :file property on a src block.
> > Let's say I have the following src block in an org file.
> > ...
> > How can I get "images/hello-world.png" in org-myexporter
Thank you for checking. I tried to reinstall the package, but it did not help,
and it caused another problem where I could not quit emacs.
Details… I ran M-x list-packages, found and deleted my org package, quit emacs.
Restarted emacs and I saw I had the builtin org (lower version: 9.4.4) and th
Rudolf Adamkovič writes:
>> Though I am not a big fan of introducing yet another customisation.
>> Maybe someone has better ideas?
>
> I struggle to understand. Why do we need a customization? If Org knows
> that some backend exists but has no execute function, why does it even
> try to execute
Felipe Lema writes:
> * ob-scheme.el (org-babel-scheme-execute-with-geiser): paste error into
> `org-babel-error-buffer-name` and setup buffer to compilation-mode
Marking this as a patch for updates.orgmode.org
Best,
Ihor
Felipe Lema writes:
> I started using guile with Org Babel and I was a little confused that errors
> weren't being reported. The attached patch will report the error the same way
> as python evaluation does.
The patch looks fine to me. Though never used scheme...
The only thing that can be im
Yasushi SHOJI writes:
> Hi,
>
> I'm writing an exporter and I'd like to get :file property on a src block.
> Let's say I have the following src block in an org file.
> ...
> How can I get "images/hello-world.png" in org-myexporter-src-block?
See org-babel-get-src-block-info. It can accept the pa
Robert Nikander writes:
> (setq org-hide-emphasis-markers t)
>
> …and the following does not render right. In the first line I see the ‘_’
> characters around “underline”, and it doesn’t underline the text.
> In the second line, it works correctly. Apparently it needs some intervening
> text (“
Joseph Vidal-Rosset writes:
> Unfortunately, all my efforts to integrate this code to export failed,
> and finally I get a JSON.parse error, (
> json-parse-unexpected-character-at-line-1-column-1-of-the-json-data )
> that I suspect to be a PHP error code.
>
> Your help is welcome.
May you provid
Allen Li writes:
> Expected:
>
> agenda tag set on bar entry
>
> Actual:
>
> agenda tag set on foo entry
Just leaving a note that it is not reproducible with latest Org.
Best,
Ihor
Eric S Fraga writes:
> for some time (years, really), I've suffered with flyspell overlays
> disappearing in comments in org documents. It never occurred to me that
> this was due to org itself so I just put up with and chalked it up to
> one of those Emacs mysteries. Today, for unrelated reaso
Hi Ross,
Am Dienstag, dem 21.12.2021 um 11:05 -0800 schrieb Jason Ross:
> Try `(setq org-context-pdf-process '("context --mode=trimsize %f"))`
> to set this as the default.
thanks a lot. The team "emacs org-mode ox-context" seems to be quite
flexible. :-)
In the meantime I debugged my context st
23 matches
Mail list logo
