Page MenuHomeSolus

Update emacs to 26.1, resolves T6456
ClosedPublic

Authored by Azphreal on May 29 2018, 2:21 AM.

Details

Summary

Highlights of this release include:

  • Limited form of concurrency with Lisp threads
  • Support for optional display of line numbers in the buffer
  • Emacs now uses double buffering to reduce flicker on the X Window System
  • Flymake has been completely redesigned
  • TRAMP has a new connection method for Google Drive
  • New single-line horizontal scrolling mode
  • A systemd user unit file is provided
  • Support for 24-bit colors on capable text terminal

Announcement email here and full changelog here.

Test Plan
  • Ran as single process and daemon modes
  • Enabled systemd user unit file
  • Tested line numbers
  • Edited several files

Diff Detail

Repository
R693 emacs
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
Azphreal created this revision.May 29 2018, 2:21 AM
Azphreal requested review of this revision.May 29 2018, 2:21 AM
Azphreal edited the summary of this revision. (Show Details)May 29 2018, 2:24 AM
sunnyflunk retitled this revision from Update emacs to 26.1 to Update emacs to 26.1, resolves T6456.May 29 2018, 2:34 AM
sunnyflunk accepted this revision.May 29 2018, 2:36 AM
sunnyflunk added a subscriber: sunnyflunk.

Thanks, note I've added 'resolves T6456' to the commit so it will also close that task.

This revision is now accepted and ready to land.May 29 2018, 2:36 AM
Closed by commit R693:56ab80b827c4: Update emacs to 26.1, resolves T6456 (authored by xeals <alex.smith@owari.cc>, committed by sunnyflunk). · Explain WhyMay 29 2018, 2:37 AM
This revision was automatically updated to reflect the committed changes.

@Azphreal note that this needs to be redone and rebased on the latest git (always run make pull prior to making any changes to a package so this doesn't happen [though it still happens a lot]).

Git was already at release 12 so it didn't merge to master (but my alias didn't exit from the failure so it pushed the branch). However, so I have nuked the branch that was created, and the repo remains at 25.3.

Sorry for that. I updated on my machine when RC-1 was released and didn't realise that the package had been bumped since then.

Should I push to this diff again or make a new one?

Should I push to this diff again or make a new one?

There is no issue pushing to this one as it never made git master