Page MenuHomeSolus

Update emacs to 26.1, resolves T6456
ClosedPublic

Authored by Azphreal on May 29 2018, 2:21 AM.
Tags
None
Referenced Files
F11005684: D3022.diff
Tue, Aug 1, 9:07 AM
F10991108: D3022.diff
Tue, Jul 25, 12:03 AM
F10987910: D3022.id7444.diff
Mon, Jul 24, 7:48 AM
F10829146: D3022.id7445.diff
Jun 4 2023, 11:17 AM
F10758217: D3022.diff
May 17 2023, 2:02 PM
F10758177: D3022.id7444.diff
May 17 2023, 1:48 PM
F10731185: D3022.id7444.diff
May 11 2023, 4:05 AM
F10731180: D3022.id7445.diff
May 11 2023, 4:04 AM
Subscribers

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
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

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 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
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