all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: "andrés ramírez" <rrandresf@hotmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>,
	"boruch_baum@gmx.com" <boruch_baum@gmx.com>
Subject: RE: using ses programatically (was: a ses question)
Date: Sun, 5 Nov 2023 16:55:46 +0000	[thread overview]
Message-ID: <PAXP192MB1608AB2F20A535B0F6E0749084ABA@PAXP192MB1608.EURP192.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <SJ1PR12MB636395EEA5EA979B625D9903A6ABA@SJ1PR12MB6363.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3229 bytes --]

Dear Andrès,

Concerning the backward compatibility you could test emacs version in smeter.el to know whether the newer ses is distibuted. Otherwise, if not distributed you could have some newer ses.el copied to the same dir as smeter.el and change the load path in smeter.el for this newer ses.el to be loaded instead of the coming with the older emacs.

FYI, I have no idea when I will push to master the ses-setq etc... changes, and no idea when this is in a new release of Emacs.

Thank you for the information about the cl-... macros, I will I have look when time allows ...

  Vincent.

PS : Maybe smeter.el would be simpler if the final sum was done by SES rather than org-table stuff.
________________________________
De : andrés ramírez <rrandresf@hotmail.com>
Envoyé : dimanche 5 novembre 2023 15:58
À : Vincent Belaïche <vincent.b.1@hotmail.fr>
Cc : emacs-devel <emacs-devel@gnu.org>; boruch_baum@gmx.com <boruch_baum@gmx.com>
Objet : Re: using ses programatically (was: a ses question)

Hi. Vincent.
My comments below.

>>>>> "Vincent" == Vincent Belaïche <vincent.b.1@hotmail.fr> writes:

    Vincent>  Dear Andrès,

    Vincent> I drafted a macro ses-setq to allow access a SES spreadsheet programatically, and I
    Vincent> updated your code to use it. This allowed to remove all the workarounds. Please note
    Vincent> that ses-setq is just a draft, far from complete. I intend to add some switches to
    Vincent> allow access the cells eaither by cell name or by row col, and to modify either value
    Vincent> or formula.

That's great. Just to mention again I have a newt-C-language app that
calls emacs this way:
--8<---------------cut here---------------start------------->8---
system ("cp workbook.ses /tmp; cp smeter.el /tmp; emacs -Q --batch -l /tmp/smeter.el /tmp/smeteroutput -f smeter/further-processing > /dev/null 2>&1");
--8<---------------cut here---------------end--------------->8---
And when the calling ends. It reads ses-output from /tmp/smeter.mail.

The C-language app does not known anything about emacs. So the logic of
calculation is within workbook.ses. That way when calculation logic
changes. The newt-C-language-App does not need to be changed. Just the
formulae within workbook.ses would be changed, which BTW is simpler than re-compiling the
newt-C-language-App.


[...]

The published version works as expected. Thanks for It.

But. I have a question. If emacs does NOT have the ses-setq
buffer (29.1 as an example). Which function calls should I do for having backward compatibility with older emacsen?.

I see ses-setq calls ses-write-cells. I added a call to ses-write-cells
after every call to ses-set-cell. But It did NOT work as expected.

Do You think It is possible to have that behaviour without using
ses-setq on older emacsen?

    Vincent> PS: I need to improve the macro, notable setting a cell value should also affect its
    Vincent> formula if any.

Ok.

BTW: JIC ses-setq is using 'cl-pushnew' this week there has been a long
discussion on emacs-devel about 'use or not to use those cl- prefixes
macros' an alternatives that are preloaded on emacs by default.

Best Regards
Andrés Ramírez

[-- Attachment #2: Type: text/html, Size: 5748 bytes --]

  reply	other threads:[~2023-11-05 16:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SJ1PR12MB6363EAEDEA36DA78E736B9DEA61EA@SJ1PR12MB6363.namprd12.prod.outlook.com>
2023-10-29 16:43 ` a ses question Vincent Belaïche
2023-10-29 21:25   ` Vincent Belaïche
2023-10-30  5:43     ` Vincent Belaïche
2023-10-30 19:03       ` andrés ramírez
2023-11-01 19:08         ` Vincent Belaïche
2023-11-01 19:23           ` Vincent Belaïche
2023-11-02 11:20             ` Vincent Belaïche
2023-11-02 11:27               ` Vincent Belaïche
2023-11-02 11:31                 ` Vincent Belaïche
2023-11-02 18:19                 ` Stefan Monnier
2023-11-03 15:54                   ` Vincent Belaïche
2023-11-03 22:13                     ` Vincent Belaïche
2023-11-04 13:46                       ` andrés ramírez
     [not found]                       ` <SJ1PR12MB636334BD471403C3F936BF25A6A4A@SJ1PR12MB6363.namprd12.prod.outlook.com>
2023-11-05 10:25                         ` using ses programatically (was: a ses question) Vincent Belaïche
2023-11-05 14:58                           ` andrés ramírez
2023-11-05 16:55                             ` Vincent Belaïche [this message]
2023-11-05 19:33                               ` andrés ramírez
2023-11-18 22:55                                 ` Vincent Belaïche
2023-11-19 19:24                                   ` andrés ramírez
2023-11-19 23:18                                     ` Vincent Belaïche
2023-11-19 23:24                                       ` Vincent Belaïche
2023-11-20  0:33                                         ` andrés ramírez
2023-12-24 11:51                                           ` Vincent Belaïche
2023-12-24 15:44                                             ` andrés ramírez
2023-12-24 21:13                                               ` Vincent Belaïche
2023-12-27 17:42                                                 ` Vincent Belaïche

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PAXP192MB1608AB2F20A535B0F6E0749084ABA@PAXP192MB1608.EURP192.PROD.OUTLOOK.COM \
    --to=vincent.b.1@hotmail.fr \
    --cc=boruch_baum@gmx.com \
    --cc=emacs-devel@gnu.org \
    --cc=rrandresf@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.