Emacs

396 readers
1 users here now

founded 1 year ago
MODERATORS
1
 
 

announce the release of Magit version 4.0.

One of the best things to happen to EMACS!

More information can be found on in the release notes.

2
3
4
5
 
 

Hello,

I am an vim user and I am used to the vim way of doing things. I started tinkering with emacs some time ago and enjoying it since because of the elisp. however I find the default keybinding kinda weird and it's hard to get used to it. we can't even vi" or ci" in emacs. also emacs doesn't have inbuilt multi cursor support.

I really want to use emacs but these things are holding me back :(

6
7
8
9
10
11
5
Emacs 29.3 released (lists.gnu.org)
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
 
 

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

12
13
14
15
16
17
18
19
20
21
22
23
24
 
 

This is a bug-fix release with no new features.

  • Changes in Specialized Modes and Packages in Emacs 29.2

    • Tramp

      • New user option 'tramp-show-ad-hoc-proxies'. When non-nil, ad-hoc definitions are kept in remote file names instead of showing the shortcuts.

  • Incompatible Lisp Changes in Emacs 29.2

    • 'with-sqlite-transaction' rolls back changes if its BODY fails. If the BODY of the macro signals an error, or committing the results of the transaction fails, the changes will now be rolled back.
25
view more: next ›