[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs Lisp's future
From: |
Richard Stallman |
Subject: |
Re: Emacs Lisp's future |
Date: |
Thu, 16 Oct 2014 14:12:18 -0400 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
I presented three solutions for handling shell-command-to-string, but
I was confusing it with another function which is a command.
shell-command-to-string is only used in Lisp programs, and probably
those programs will not show that text to a user except in error messages.
Perhaps it should always do strict decoding.
Can you present a real example of using shell-command-to-string
that really needs to do flexible decoding?
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
- Re: Emacs Lisp's future, (continued)
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/13
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/13
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/13
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/14
- Re: Emacs Lisp's future, David Kastrup, 2014/10/14
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/15
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/15
- Re: Emacs Lisp's future, David Kastrup, 2014/10/15
- Re: Emacs Lisp's future,
Richard Stallman <=
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/12
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/09
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/10
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/10
Re: Emacs Lisp's future, Mark H Weaver, 2014/10/10
Re: Emacs Lisp's future, Richard Stallman, 2014/10/10