From: Tom Tromey <tom@tromey.com>
To: "Simen Heggestøyl" <simenheg@gmail.com>
Cc: steve@sanityinc.com, tom@tromey.com, dgutov@yandex.ru,
27881@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#27881: New major mode: Less mode
Date: Tue, 01 Aug 2017 20:16:59 -0600 [thread overview]
Message-ID: <87k22m90is.fsf@tromey.com> (raw)
In-Reply-To: <1501437183.13205.0@smtp.gmail.com> ("Simen \=\?utf-8\?Q\?Heggest\?\= \=\?utf-8\?Q\?\=C3\=B8yl\=22's\?\= message of "Sun, 30 Jul 2017 19:53:03 +0200")
>>>>> "Simen" == Simen Heggestøyl <simenheg@gmail.com> writes:
Simen> +(defcustom less-css-lessc-command "lessc"
Simen> + "Command used to compile LESS files.
Simen> +Should be lessc or the complete path to your lessc executable,
Simen> + e.g.: \"~/.gem/ruby/1.8/bin/lessc\""
Simen> + :type 'file
Simen> + :group 'less-css
Simen> + :safe 'stringp)
Simen> +
Simen> +;;;###autoload
Simen> +(defcustom less-css-compile-at-save nil
Simen> + "If non-nil, the LESS buffers will be compiled to CSS after each save."
Simen> + :type 'boolean
Simen> + :group 'less-css
Simen> + :safe 'booleanp)
It seems dangerous to me to mark these both as safe. A file could
specify a dangerous command and then say it's ok to run it on save.
Probably the command should not be :safe.
Maybe the other variables defined after this should also not be safe.
Tom
next prev parent reply other threads:[~2017-08-02 2:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 17:53 bug#27881: New major mode: Less mode Simen Heggestøyl
2017-07-30 20:59 ` Stefan Monnier
2017-07-31 6:39 ` Steve Purcell
2017-07-31 12:44 ` Stefan Monnier
2017-07-31 2:02 ` Glenn Morris
2017-07-31 4:32 ` Marcin Borkowski
2017-08-03 17:47 ` Simen Heggestøyl
2017-08-04 21:33 ` Richard Stallman
2017-08-02 2:16 ` Tom Tromey [this message]
2017-08-03 17:50 ` Simen Heggestøyl
2017-08-03 20:08 ` Stefan Monnier
2017-08-10 22:53 ` Simen Heggestøyl
2017-08-14 10:06 ` Stefan Monnier
2017-08-15 10:33 ` Simen Heggestøyl
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=87k22m90is.fsf@tromey.com \
--to=tom@tromey.com \
--cc=27881@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=monnier@iro.umontreal.ca \
--cc=simenheg@gmail.com \
--cc=steve@sanityinc.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.