From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: on ``An Introduction to Programming in Emacs Lisp''
Date: Tue, 2 Feb 2016 03:43:36 -0800 (PST) [thread overview]
Message-ID: <0ec96568-4fa3-47e8-a224-722dc842181a@googlegroups.com> (raw)
In-Reply-To: <mailman.3404.1454397765.843.help-gnu-emacs@gnu.org>
On Tuesday, February 2, 2016 at 12:52:47 PM UTC+5:30, Marcin Borkowski wrote:
> On 2016-02-02, at 01:28, Emanuel Berg wrote:
>
> > Marcin Borkowski writes:
> >
> >> I'd like to point out that one nice benefit of
> >> compiling from source (apart from staying on the
> >> bleeding edge) ...
> >
> > There can be many definitions of "staying on the
> > bleeding edge". One is: using software to be active,
> > creative and productive with *your own projects* that
> > perhaps nobody else knows about, until you release it
> > for everyone to see and (sometimes) use.
> >
> > Using the latest releases of everything, including
> > hardware components, is something some people take
> > pride in.
> >
> > But often this is actually something that one
> > shouldn't do because it is an obstacle to the own
> > activity which benefits from reliable, familiar tools.
>
> Fair enough.
>
> I have to say, though, that the alleged unreliability of the development
> version of Emacs has yet to hit me.
See my other thread on python mode.
In summary: Builtin python mode is giving various unfriendly messages in
emacs 25 not 24
next prev parent reply other threads:[~2016-02-02 11:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 18:08 on ``An Introduction to Programming in Emacs Lisp'' Daniel Bastos
2016-01-28 23:58 ` Emanuel Berg
2016-01-29 2:11 ` Robert Thorpe
2016-01-29 12:38 ` Filipp Gunbin
2016-01-29 13:20 ` Paul Smith
2016-01-29 20:46 ` Emanuel Berg
2016-01-29 22:20 ` Marcin Borkowski
2016-01-30 9:05 ` Emanuel Berg
2016-01-30 9:57 ` Marcin Borkowski
2016-01-30 0:23 ` Robert Thorpe
2016-01-30 9:22 ` Emanuel Berg
2016-01-30 14:19 ` Robert Thorpe
2016-01-31 20:45 ` Emanuel Berg
2016-02-01 11:07 ` Marcin Borkowski
2016-02-02 0:28 ` Emanuel Berg
2016-02-02 7:22 ` Marcin Borkowski
2016-02-02 22:59 ` Emanuel Berg
2016-02-03 9:25 ` Marcin Borkowski
2016-02-03 20:00 ` Emanuel Berg
2016-02-04 16:37 ` Nick Dokos
[not found] ` <mailman.3524.1454529667.843.help-gnu-emacs@gnu.org>
2016-02-03 20:12 ` Pascal J. Bourguignon
2016-02-04 1:15 ` Emanuel Berg
[not found] ` <mailman.3489.1454491565.843.help-gnu-emacs@gnu.org>
2016-02-03 11:43 ` Daniel Bastos
2016-02-03 20:08 ` Emanuel Berg
[not found] ` <mailman.3404.1454397765.843.help-gnu-emacs@gnu.org>
2016-02-02 11:43 ` Rusi [this message]
[not found] ` <mailman.3321.1454324852.843.help-gnu-emacs@gnu.org>
2016-02-01 12:07 ` on specifying the C source code directory (Was: Re: on ``An Introduction to Programming in Emacs Lisp'') Daniel Bastos
2016-02-01 12:38 ` Marcin Borkowski
2016-02-01 12:32 ` tomas
2016-02-01 13:54 ` Kaushal Modi
2016-02-01 16:42 ` on specifying the C source code directory Daniel Bastos
2016-02-02 0:17 ` Emanuel Berg
2016-02-02 7:23 ` Marcin Borkowski
2016-02-02 23:04 ` defvar and "assignment to free variable" (was: Re: on specifying the C source code directory) Emanuel Berg
[not found] ` <mailman.3326.1454332068.843.help-gnu-emacs@gnu.org>
2016-02-02 11:57 ` on specifying the C source code directory Daniel Bastos
2016-02-02 11:52 ` tomas
[not found] ` <mailman.3168.1454113433.843.help-gnu-emacs@gnu.org>
2016-01-30 3:20 ` on ``An Introduction to Programming in Emacs Lisp'' Rusi
[not found] ` <mailman.3104.1454025553.843.help-gnu-emacs@gnu.org>
2016-01-29 20:29 ` Javier
2016-01-30 3:26 ` Pascal J. Bourguignon
2016-01-30 9:02 ` Emanuel Berg
2016-01-30 15:29 ` Eli Zaretskii
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=0ec96568-4fa3-47e8-a224-722dc842181a@googlegroups.com \
--to=rustompmody@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).