From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: Liwei Ma <liwei.ma@gmail.com>
Cc: "emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
Subject: Re: When will emacs 27.1 be officially released?
Date: Tue, 30 Jun 2020 16:34:56 +0200 [thread overview]
Message-ID: <CAEtmmewZgS+pgP84buqrnLwziB5cUhbVTCgSTaemyN+h5B33-g@mail.gmail.com> (raw)
In-Reply-To: <CAMH6LnBHvA0AGPbuTPthaLzNCqMCD6NB4SK859Gnjt813Ga8mQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
> We wait for a new version too long this year:)
I have a good experience with compiling and using emacs-NextRelNr branches.
Since at least emacs-25 (~4 years). I made myself a fish-shell script
https://github.com/Bost/dotfiles/blob/master/fish/functions/make-emacs.fish
to compile the code and git-tag it, if there's a change in the code files
since my last compilation. (The script doesn't proceed with compilation if
only documentation changed.) I tag the repo just in case something's
broken, so I can just checkout the previous tag and rerun my script. (The
script is not 100% maintenance-free, but I don't bother editing it now and
then.)
I use spacemacs (daily), mostly for clojure development. And I update
spacemacs, plus installed packages almost daily. Everything works fine and
I don't encounter any problems more than once a year, including problems
with packages.
The only problem I have is with freezes when editing larger files (> ~1MB)
especially with long lines. But that's a general and long standing issue.
In such a case I just `killall emacs` and try to run `emacs
--no-init-file`. It helps in about 50% of the situations.
[-- Attachment #2: Type: text/html, Size: 1374 bytes --]
prev parent reply other threads:[~2020-06-30 14:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 2:52 When will emacs 27.1 be officially released? Liwei Ma
2020-06-30 3:55 ` Eli Zaretskii
2020-06-30 8:12 ` tomas
2020-06-30 9:51 ` Kévin Le Gouguec
2020-06-30 16:58 ` Eli Zaretskii
2020-06-30 18:52 ` Paul Eggert
2020-06-30 19:06 ` Eli Zaretskii
2020-06-30 22:17 ` Paul Eggert
2020-06-30 22:31 ` Dmitry Gutov
2020-07-01 0:03 ` Paul Eggert
2020-07-01 14:29 ` Eli Zaretskii
2020-07-01 17:47 ` Dmitry Gutov
2020-07-01 17:52 ` Paul Eggert
2020-07-01 17:55 ` Dmitry Gutov
2020-07-01 18:13 ` Eli Zaretskii
2020-07-01 18:16 ` Dmitry Gutov
2020-07-01 18:12 ` Eli Zaretskii
2020-07-01 14:33 ` Eli Zaretskii
2020-07-02 3:49 ` Richard Stallman
2020-07-02 13:04 ` Eli Zaretskii
2020-07-03 2:21 ` Richard Stallman
2020-07-02 20:29 ` Tassilo Horn
2020-07-02 20:36 ` Paul Eggert
2020-07-02 20:55 ` Tassilo Horn
2020-07-04 2:53 ` Richard Stallman
2020-07-04 6:41 ` Eli Zaretskii
2020-07-05 2:35 ` Richard Stallman
2020-07-05 14:33 ` Eli Zaretskii
2020-07-03 6:05 ` Eli Zaretskii
2020-07-03 7:24 ` Tassilo Horn
2020-07-03 11:59 ` Eli Zaretskii
2020-07-04 2:52 ` Richard Stallman
2020-06-30 22:09 ` Kévin Le Gouguec
2020-07-01 14:49 ` Eli Zaretskii
2020-07-02 9:00 ` Kévin Le Gouguec
2020-07-02 13:12 ` Eli Zaretskii
2020-07-02 13:44 ` Kévin Le Gouguec
2020-07-03 0:48 ` Do pretests reach end users? (was: When will emacs 27.1 be officially released?) Dmitry Alexandrov
2020-07-03 6:21 ` Eli Zaretskii
2020-07-03 9:59 ` Do pretests reach end users? Dmitry Gutov
2020-07-03 11:43 ` Eli Zaretskii
2020-07-03 20:23 ` Dmitry Gutov
2020-07-04 6:15 ` Eli Zaretskii
2020-07-04 1:31 ` Dmitry Alexandrov
2020-07-04 6:32 ` Eli Zaretskii
2020-07-05 4:18 ` Dmitry Alexandrov
2020-07-04 11:11 ` Phillip Lord
2020-07-05 4:23 ` Dmitry Alexandrov
2020-07-05 21:15 ` Phillip Lord
2020-07-05 16:55 ` Sean Whitton
2020-06-30 13:01 ` When will emacs 27.1 be officially released? Basil L. Contovounesios
2020-06-30 14:06 ` Stefan Monnier
2020-06-30 14:28 ` Eli Zaretskii
2020-06-30 14:34 ` Rostislav Svoboda [this message]
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=CAEtmmewZgS+pgP84buqrnLwziB5cUhbVTCgSTaemyN+h5B33-g@mail.gmail.com \
--to=rostislav.svoboda@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=liwei.ma@gmail.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 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).