This is very useful, especially being able to see the output of BiBTeX,
say. Thank you.
--
: Eric S Fraga, with org release_9.5.3-508-ge268e4 in Emacs 29.0.50
On Sunday, 22 May 2022 at 08:57, Uwe Brauer wrote:
> 1. org-table-recalculate-buffer-tables
> 2. org-table-iterate-buffer-tables
> Can anybody please enlighten me?
My understanding is: the first will be suitable if there is a simple
one-way transfer of data and the tables are in an order t
Dear Ihor,
> However, this (delete-char 1) somehow deletes 2!! chars instead of
> 1. This should be some tricky Emacs issue (bug?). In any case, I am
> not ready to dig into what is going on in Emacs. I do not think that
> such problem is going to appear during normal Emacs usage. At least, I
> wa
"Samuel Banya" writes:
> Hey there,
> So I took a look at the following link recently as I finally have had time
> again over the past couple of months since I've been dealing with a lot of
> personal family stuff, and got some time back again.
Thanks for your interest in contributing!
> Can
On Friday, 20 May 2022 at 20:18, ed...@openmail.cc wrote:
> Is this the expected behaviour? Thanks again :) .
Well, looking at the code, if any of the :height or :width attributes
have been specified explicitly, the defaults for height and width are
ignored. If you want to specify both, you will
Tak Kunihiro writes:
> I still see the problem with GNU Emacs 29.0.50 (build 8,
> x86_64-apple-darwin21.5.0, NS appkit-2113.50 Version 12.4 (Build 21F79))
> of 2022-05-23 with org-version 9.5.3.
>
> I create org-tables and revise these everyday. On duplication of a
> cell, I hit S- often. The pr
Hi Eric,
> But given that you also want to keep the aspect ratio, I am curious as
> to why you would need/want to specify both?
Just on this, the `keepaspectratio' option of `graphicx' could be relevant here.
All the best,
Timothy
Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> Sorry for this delay. Then, can you send them a followup email reminder?
>> If they do not reply within another week, we will contact FSF directly.
>
> Thank you. I sent a followup email just now, FYI.
FYI, I did receive a reply after the
Rudolf Adamkovič writes:
> FYI, I did receive a reply after the follow-up mail. I signed the papers and
> sent them back to FSF just now. I will revive the thread once FSF does its
> part. Hopefully, I will not wait for yet another (third) month. :)
Do not wait one month. Just 5 working days.
Thanks all for your help!
On 5/20/22 9:44 PM, Ihor Radchenko wrote:
Dear Craig, ... or provide plain/text handler in ~/.mailcap.
OK, I did a first-try on this and was unsuccessful, but I'm sure it's
user error. I need to refresh my knowledge on how to customize
user-local mime database, and
I guess maybe I should have given a little better description of what I
tried that did NOT work? But it's a little off-topic for this mailing
list. Nevertheless, here it is...
I created a ~/.mailcap file and put this in it, which I cut and pasted
from /etc/mailcap:
application/x-shellsc
Everything I mentioned so far has been my Bionic desktop. Which,
incidentally was an upgrade from Xenial, not a clean install. But... in
my Focal headless container, if I run:
>$ run-mailcap myscript
it invokes emacs. Yay! It works! DISPLAY, EDITOR, and VISUAL are all
unset or empty.
Hi all,
I think this idea was suggested by Ihor in a thread from a few months
ago (I don't remember which one), but since other topics were discussed,
the idea remained a bit in limbo. I still find the idea very
interesting, and I think it would be very productive for Org to have a
multipurpose in
On 5/23/22 10:14 AM, Craig STCR wrote:
>$ run-mailcap myscript
it invokes emacs. Yay! It works!
Double DOH! Forget what I said. It invokes vim, lol. That *is* what I
would expect. Sorry for the noise. I need to think a little more
before I hit .
On Mon, May 23, 2022 at 10:33 AM Juan Manuel Macías
wrote:
> I think this idea was suggested by Ihor in a thread from a few months
> ago (I don't remember which one), but since other topics were discussed,
> the idea remained a bit in limbo. I still find the idea very
> interesting, and I think i
Craig, discussing the issue with Ihor, I sent some messages to the mail
list only without your address in Cc. You may check complete thread at
https://list.orgmode.org
On 23/05/2022 19:40, Craig STCR wrote:
OK, I did a first-try on this and was unsuccessful, but I'm sure it's
user error. I
Ypo,
> (defun salto ()
> (interactive)
> (if posicion 1
> (posicion2)
> (if posicion 2
> (posicion3)
> (if posicion 3
> (posicion1)
your function =salto= may be using =if= incorrectly. try marking that
=defun= and hitting TAB to justify it. my guess is, t
Hi
The following code block is nicely displayed
#+begin_src matlab :exports results :eval never-export :results output latex
disp('P(\text{Covid19}|\text{+})&=\frac{P(\text{+}|\text{Covid19})P(\text{Covid19})}{P(\text{+}|\text{Covid19})P(\text{Covid19})+P(\text{+}|\text{No-Covid19})P(\text{No
On Mon, May 23, 2022 at 09:46:09AM -0700, Greg Minshall wrote:
> Ypo,
>
> > (defun salto ()
> > (interactive)
> > (if posicion 1
You are comparing the value of posicion to 1?
Then it should probably be "(if (= posicion 1) ...)" or
"(if (equal posicion 1) ...)" or something like that.
Cheers
Hello Uwe
> On Monday, 23 May 2022 at 19:24, Uwe Brauer wrote:
Sorry I don't have matlab and I have never used the solutionorbox
environment, but I believe you can generate latex directly. For example
with R I can to the following.
#+begin_src R :exports results :eval yes :results output latex
Hi, Kaushal, thanks for all your interesting comments,
Kaushal Modi writes:
> The challenging part will be deciding the syntax so that there are no
> false matches.
>
> May be reserve "inline_" for inline blocks?
>
> e.g. inline_[options]{text} ?
It seems to me the most consistent option, if we
I've not got a lot to add here. I'm not against the idea, but Juan makes
some points below which I think are particularly important and wanted to
add weight to them!
Juan Manuel Macías writes:
> Hi, Kaushal, thanks for all your interesting comments,
>
> Kaushal Modi writes:
>
>> The challengin
Uwe Brauer writes:
> However when I wrap a solutionorbox around it (which I need when
> exporting to latex) all text between the «+»
> gets a strikeout.
>
>
> #+begin_solutionorbox
> #+begin_src matlab :exports results :eval never-export :results output latex
> disp('P(\text{Covid19}|\text{+})&=
Tim Cross writes:
>> I think a major issue would also be how to properly compact <[options]>
>> so as not to result in too overloaded syntax. Maybe something like:
>>
>> [latex(list of attributes) html(list of attributes)...]
>>
>> ?
>>
>> But that is an abuse of direct formatting, which I think
Hi Tim,
Tim Cross writes:
>> But that is an abuse of direct formatting, which I think should always be
>> avoided, especially in a format-agnostic environment like Org, which is
>> more of a logician than a typesetter :-)
>
> I think this is a really important point. Whenever we add formatting
>
On Tuesday, 24 May 2022 at 10:51, Timothy wrote:
> To me, this is another reason for comment and #+attr_X lines not to
> break paragraphs [...].
And, in fact, if this were true (which I would like), I personally would
see no reason for having inline special blocks.
Just my 2¢.
--
: Eric S Fraga
26 matches
Mail list logo
