From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: Stefan Monnier <monnier@iro.umontreal.ca> , emacs-devel@gnu.org
Subject: Re: SES local variables to define printers
Date: Sun, 26 May 2013 22:25:58 +0200 [thread overview]
Message-ID: <801u8tcwtl.fsf@gmail.com> (raw)
Stefan Monnier a écrit :
>> Well, it also means that your .emacs will grow endlessly as you create
>> new sheets, and also that you cannot archive the sheet+printer in the
>> same batch easily.
>
> I find it odd that the set of printer functions would grow endlessly
> with the number of sheets; I'd expect there to be a fairly limited
> number of them, but maybe they differ in "minor" details.
>
Well, mainly some surounding of the information, some number formatting,
etc... as you have a great number of possible combinations, that would
really make things grow endlessly.
In fact I think that the simplest/safest way would be if the printer
would be some string, that SES would interprete to build the
function. The thing is that I need to extend the format %d %f and on on
to cover Calc objects. This is something which I had already being
thinking about for some time, but I have not yet dared go into it.
> But it sounds like you'd want to extend SES so that you can store/share
> definitions of functions in the SES file.
>
> E.g. when you do `p (lambda (...)) RET' SES could immediately ask you to
> name that function and save the result somewhere in the file.
>
That would not really make it safer because any hacker could find the
`somewhere in the file' and put some malicious definition there.
>> border effect and without any loop structure.
>
> Actually, loop structure doesn't sound problematic w.r.t safety.
>
>
My concern was more about getting the system stuck, but you still have
the C-g
> Stefan
>
Vincent.
next reply other threads:[~2013-05-26 20:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 20:25 Vincent Belaïche [this message]
2013-05-27 1:35 ` SES local variables to define printers Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2013-05-30 15:36 Vincent Belaïche
2013-05-30 17:15 ` Stefan Monnier
2013-05-30 7:24 Vincent Belaïche
2013-05-30 5:50 Vincent Belaïche
2013-05-30 13:20 ` Stefan Monnier
2013-05-28 4:38 Vincent Belaïche
2013-05-28 4:57 ` Stefan Monnier
2013-05-26 7:16 Vincent Belaïche
2013-05-26 18:02 ` Stefan Monnier
2013-05-25 20:43 Vincent Belaïche
2013-05-26 1:17 ` Stefan Monnier
2013-05-24 5:53 Vincent Belaïche
2013-05-24 5:46 Vincent Belaïche
2013-05-24 5:45 Vincent Belaïche
2013-05-24 13:28 ` Stefan Monnier
2013-05-23 20:52 Vincent Belaïche
2013-05-23 21:35 ` Davis Herring
2013-05-24 1:06 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=801u8tcwtl.fsf@gmail.com \
--to=vincent.b.1@hotmail.fr \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).