4ffy

joined 2 years ago
[–] 4ffy@lemmy.ml 28 points 3 months ago* (last edited 3 months ago)

The reason that Doom is so portable goes beyond Linux and is an artefact of its development. id developed Doom on NeXTSTEP (i.e. Unix) machines and obviously targeted DOS. This is pretty unique among DOS games at the time and required id to write as much code as possible in a platform agnostic way. This means that the main engine does not care about where it is running and the usual DOS hacks are contained to DOS-specific files. In order to port Doom to a new platform, ideally one only needs to rewrite the system-specific implementation files for video, sound, filesystem access, etc., and this mostly holds true today. (These files are prefixed with i_ in the Doom source).

The Linux port is just one of many versions developed at the time. I don't believe that it was commercially released; it was more of a portability test. The reason that the Linux version was chosen for the source release over the DOS version was because it didn't rely on the proprietary DMX sound library that the DOS port used.

 

This release brings a host of user-facing refinements to an already stable base, as well as some impressive new features. There is a lot to cover, so take your time reading these notes.

Special thanks to Jean-Philippe Gagné Guay for the numerous refinements to parts of the code base. Some of these are not directly visible to users, but are critical regardless. In the interest of brevity, I will not be covering the most technical parts here. I mention Jean-Philippe’s contributions at the outset for this reason. Though the Git commit log is there for interested parties to study things further.

1
Emacs 29.3 released (lists.gnu.org)
 

cross-posted from: https://lemm.ee/post/27699104

From the NEWS file: Emacs 29.3 is an emergency bugfix release intended to fix several security vulnerabilities described below.

  • Arbitrary Lisp code is no longer evaluated as part of turning on Org mode. This is for security reasons, to avoid evaluating malicious Lisp code.

  • New buffer-local variable 'untrusted-content'. When this is non-nil, Lisp programs should treat buffer contents with extra caution.

  • Gnus now treats inline MIME contents as untrusted. To get back previous insecure behavior, 'untrusted-content' should be reset to nil in the buffer.

  • LaTeX preview is now by default disabled for email attachments. To get back previous insecure behavior, set the variable 'org--latex-preview-when-risky' to a non-nil value.

  • Org mode now considers contents of remote files to be untrusted. Remote files are recognized by calling 'file-remote-p'.

 

This is the first pretest for what will become the 29.2 release of Emacs, which is primarily a bugfix release.

[–] 4ffy@lemmy.ml 5 points 1 year ago

Xremap, despite the name, supports both X and Wayland, and can be used to move modifier keys around. Configuration is done with YAML but is otherwise pretty easy. I personally use it for full Emacs keybind emulation.

[–] 4ffy@lemmy.ml 142 points 1 year ago* (last edited 1 year ago) (16 children)

This might be the first time I've ever seen something productive happen in the Phoronix forums. I love that place. Go to any topic with more than about a dozen posts and it's almost guaranteed to be a flame war. Genuinely one of the funniest places on the Internet.

Check out this one. It took like three posts!

1
Emacs 29.1 Released (lists.gnu.org)
submitted 1 year ago* (last edited 1 year ago) by 4ffy@lemmy.ml to c/emacs@lemmy.ml
 

Available at your local GNU mirror and, depending on your OS, perhaps soon your favorite package manager repository. A full list of features and changes can be found in the NEWS file.

view more: next ›