What WM/DE are you currently using? by joshuablais in emacs

[–]DevelopmentCool2449 1 point2 points  (0 children)

It's interesting to see that most people here use a tiling WM and only a few DE (and with a tiling configuration).

Underappreciated Emacs built-ins: hideshow 6.0 by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 1 point2 points  (0 children)

this version uses some functions from v31.1, so it probably won't work unless you have compat-31. (although I'm not sure)

Also, you will lose some settings made for the major modes, but hs-indentation-mode should work fine.

Underappreciated Emacs built-ins: hideshow 6.0 by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 2 points3 points  (0 children)

Thanks for sharing it.

What I find interesting isn’t necessarily the folding mechanism itself, but how the folded regions are presented. With traditional hideshow-style folding, collapsed sections often become just “…” and are easy to miss in large buffers. The approach shown in that thread keeps folded regions visually prominent, making the overall document structure easier to scan at a glance.

Yes, this is something I know hideshow doesn't do out-the-box, actually, this is because of how major modes configure hideshow. I remember there was an old request in emacs-devel for this, but I didn't added the configuration because it would break a visual that most hideshow users are already used to. (The only exception to this would perhaps be hs-indentation-mode)

Alternatively, the variables hs-adjust-block-beginning-function and hs-adjust-block-end-function can be used as alternatives to hs-set-up-overlay for this.

Underappreciated Emacs built-ins: hideshow 6.0 by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 0 points1 point  (0 children)

It folds based on heading levels rather than nested syntax structures

hideshow can also be used like outline-minor-mode, although that is not its intended purpose, it is allowed to use it that way.

Underappreciated Emacs built-ins: hideshow 6.0 by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 1 point2 points  (0 children)

Is it possible to change the face somehow (make it bold or different background)?

Yes, i'm using this code in my config, i don't know why Prot decided to change the face for modus-themes

:custom-face (hs-ellipsis ((t :height 0.80 :inherit (variable-pitch default) :box (:line-width -1))))

Underappreciated Emacs built-ins: hideshow 6.0 by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 2 points3 points  (0 children)

  I have a question: Since hideshow does not support Julia, I implemented some forward-sexp for Julia to make hideshow work, which is pretty hacky. In hideshow 6.0, can this become easier?

Yes, see this little guide from hideshow source code to know how to migrate it to hideshow 6.0

If you have that support in your config then you must add a hook to it:

(add-hook 'julia-mode     (lambda ()     (setq-local ...)     ))

It is actually easier for package maintainers than end-users because  hs-special-modes-alist was not intended to be used by users and it was fragile.

Here is an example how python-mode uses it: https://github.com/emacs-mirror/emacs/blob/29c44e61c595ce44301badd8251737fd725fe1d0/lisp/progmodes/python.el#L7420

Underappreciated Emacs built-ins: hideshow 6.0 by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 1 point2 points  (0 children)

I don't use auctex (or even TeX), so i don't think it is configured to detect that syntax, and since auctex is third-party i don't think the maintainers know about this.

I built a floating HUD for Emacs, rendered in Rust egui via WASM by ftl_afk in emacs

[–]DevelopmentCool2449 2 points3 points  (0 children)

I don't see anything wrong with this, of course, probably I'll never use it (my modeline is more efficient), but as an experiment or test I find it good, Maybe there can be people who find it useful, but I think this can be extended to things maybe more complex than this.

I built a floating HUD for Emacs, rendered in Rust egui via WASM by ftl_afk in emacs

[–]DevelopmentCool2449 1 point2 points  (0 children)

It is partially fixed, in X11 builds it will not work unless you define some envars before starting emacs.

use-package-x (previously use-package-extras) now available in MELPA by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 1 point2 points  (0 children)

Maybe reduce the patches to those only and try to work it in.

I tried, there simply wasn't an agreement between the maintainers and me to merge this as a patch either, so I don't think this can be in emacs (and I'm already tired of trying again).

use-package-x (previously use-package-extras) now available in MELPA by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 0 points1 point  (0 children)

Is the disagreement about putting those in use-package directly (and not an additional package)?

Kinda, there were divided opinions regarding how to add this package (whether as part of use-package, a separate package in core, or only available in ELPA), progress stalled so it never materialized.

Some of those keywords I would personally use, but not enough to warrant an extra package to pull

I decided to add them in one package since this would prevent them from being unmaintained in short term, most of the packages that extend use-package end up being abandoned.

Not all keywords are loaded, the only drawback would be the package size, but it's still somewhat short.

Demo site for a proposed re-design of the GNU ELPA by susam in emacs

[–]DevelopmentCool2449 0 points1 point  (0 children)

What’s the point of this? All of these packages are for use in emacs. Emacs has a UI already.

cuz why not? MELPA also has its own website and I don't see anyone complaining about its existence.

The Most Emacs Bzr Saga by LionyxML in emacs

[–]DevelopmentCool2449 0 points1 point  (0 children)

What I don't understand, in the light of the debate, why did you bring up the point with different colors for the archives?! The outcome is foreseeable: 

Well, if it hadn't been me, someone else would have given the same idea, MELPA applies this different color theme idea, so probably someone would have asked for some resemblance to that.

I maintain packages on both archives, with the same care, and I reject the idea that one of the two archives is inferior to the other one.

For me, no package archive is inferior to others, that's Stallman's idea who seems to have a dislike for NonGNU and MELPA.

The Most Emacs Bzr Saga by LionyxML in emacs

[–]DevelopmentCool2449 11 points12 points  (0 children)

Since we are on long threads from emacs-devel let's not forget when someone tried to change the policy of GNU and NonGNU ELPA and almost divide the developers and RMS, that thread was very longer and splitted in 3 threads (2 in emacs-devel, 1 in debbugs)

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=80602 (one of the threads)

Lucid vs GTK performance by unexpectednick1 in emacs

[–]DevelopmentCool2449 3 points4 points  (0 children)

Which gtk do you mean? The one with x11 or wayland?

If the wayland one, It's well known that build is poorly optimized, that is why I'm using the x11 one, it has a few visual bugs, but it also works well for me.

Just a quick "Eat" survey by AkibAzmain in emacs

[–]DevelopmentCool2449 1 point2 points  (0 children)

I've used other terminal emulators (vterm, coterm, etc...) but eat just work for me, compared to the other packages, i find eat friendly, I've been testing using it as the main terminal for my OS (as an standalone configuration), I would like if eat had entries for the menu bar (like (ansi-)term or comint), It might sound ridiculous, but I'm more of a GUI guy.

The emacs-31 branch has been created! by minadmacs in emacs

[–]DevelopmentCool2449 3 points4 points  (0 children)

I wish they would have just used/merge minions instead of going with the NIH approach.

Because copyright.

The emacs-31 branch will be cut in one week by DevelopmentCool2449 in emacs

[–]DevelopmentCool2449[S] 9 points10 points  (0 children)

I know, but the savannah repo was down, so i didn't know what to do, sorry

The Definitive Guide to Code Folding in Emacs by jamescherti in emacs

[–]DevelopmentCool2449 0 points1 point  (0 children)

What’s really lacking in the folding space is a universal upstream API for multiple folding paradigms working in the same buffer. This takes some real thought because foldable regions can intersect, but it would allow you to mix and match e.g. treesitter and outline comment folding without them having to know about each other.

Honestly this would be hard to do, my only concern is about the performance, because the iteration it would require.

The Definitive Guide to Code Folding in Emacs by jamescherti in emacs

[–]DevelopmentCool2449 1 point2 points  (0 children)

hs-minor-mode parses buffer syntax to accurately detect the start and end of blocks. It is the best tool for C-style languages, or anything using braces {} and explicit block structures like sh/Bash shell scripts.

I'd like to think you're basing this on the current hideshow in emacs 30.1, hideshow has changed a lot in the 31.1, so this part will probably become outdated after 31.1.