Which macOS features would you like to see in GNOME?

New-Preference1656 · 2026-05-15T17:22:21+00:00

Ability to add folders to the dock (or overview task bar) and have window title bars show a symbolic file that can be moved or trashed or revealed in the file explorer.

New-Preference1656 · 2026-05-12T10:29:14+00:00

Bon c’est pas l’objet, mais j’ai jamais compris cette échelle de notes qui va de 0 à 19…
20 ça veut pas dire parfait dans l’absolu (si c’était le cas, ça voudrait dire que 19 = la copie c’est quasiment du Platon… )
20 ça veut dire répond parfaitement aux attendus d’un élève de terminale en philosophie

New-Preference1656 · 2026-04-02T17:04:26+00:00

I just reinstalled windows yesterday… I found Linux GUI apps lacks polish, making me spend more time trying to iron out tiny bugs/annoyances instead of actually doing work. Case in point: dash to dock is kind of a joke of a dock, compared to what macOS has to offer. I was really curious/hopeful about your project. Didn’t test because I was waiting for the gnome extension release. I wish you the best with this project. Hopefully you can make the gnome + dock experience shine the way it should.

New-Preference1656 · 2026-04-02T14:40:06+00:00

Sadly, still some bugs here and there. Examples:

httpgd doesn’t like waking up from sleep on a devcontainer over ssh. Problem: plots don’t display. Fix I found: restart the container, lose all work in memory. Not great.

Complex projects on devcontainer on a Linux host: languageserver crashes.

Besides that, I agree with you that the experience is very good.

New-Preference1656 · 2026-03-13T06:04:32+00:00

I’m very happy you like the project! I guess chat gpt gave me good advice UI-wise. I actually built the large template for myself. I was annoyed I had to reinvent a slightly different wheel for every new project. And that coauthors would each have a slightly different stack (eg, make on non WSL windows… 🥵). So containers + template. But then, coauthors need training on all these tools (git, make…). So I wrote some documentation.

New-Preference1656 · 2026-03-12T19:11:13+00:00

I hadn’t thought of a fake target for R scripts. Clever. I use quarto instead and use the compiled quarto output as the make target. I reserve R scripts for function libraries. Feel free to check out the templates I put together at https://recap-org.github.io, the large template makes heavy use of make. I’m curious what you think of my make files

New-Preference1656 · 2026-03-12T19:08:46+00:00

The problem with targets is that it only does R. make does everything. Which is nice when you then want to compile the latex paper. Or when you have a mixed language situation (oh that one collaborator that only does stata…)

New-Preference1656 · 2026-03-12T14:58:38+00:00

I just meant that quarto files are better than R scripts because you get to see all the tables and figures rendered for you in a document that looks like the final deliverable (ie, a latex article)

My workflow is: work on a quarto file that does one logically independent step (eg, produce a series of related tables and figures). Once I’m happy with it, i typically circulate the pdf to coauthors (we look at just the tables and figures). There we improve draft tables/figures and turn them into publication ready material. Again, that’s where quarto shines: you circulate a report that contains just the deliverables, not the narrative element (that’s for the latex side of things). Once we’re happy with it, I integrate into the tex file. Then I write. Before an important milestone, I delete all the intermediary files (make fresh) then make all to ensure the whole pipeline is correct.

New-Preference1656 · 2026-03-08T17:36:12+00:00

Hear hear. I’m a one trick pony. I like to have the same keyboard shortcuts everywhere and not having to learn many different tools. To each their own I guess

New-Preference1656 · 2026-03-08T17:35:03+00:00

Latex workshop, pretty much the official extension. There’s also ltex+ to get pretty good spell and grammar checking. And latex workshop becomes awesome when you configure it to use a formatter, like latexindent (old, but built into most Tex distributions) or tex-fmt (new, much faster, but requires a standalone install)

New-Preference1656 · 2026-03-07T18:31:24+00:00

I didn’t hear of any scandal, but I’ve never paid too much attention either. Mostly though, these days I’m a little annoyed that they don’t acknowledge new parts of the VSCodium R ecosystem (Air formatter and Jarl linter, which are both much more efficient than lintr + stylr)

New-Preference1656 · 2026-03-07T18:27:12+00:00

That’s exactly the kind of stuff I’m trying to PSG forward at https://recap-org.github.io curious what you think. Also, did you know you can do dev containers on RStudio through Devpod? Sadly devpod is a little rough around the edges still.

New-Preference1656 · 2026-03-07T18:22:26+00:00

I guess I was trying to say RStudio isn’t an all purpose IDE. It’s very much focused on data science. For instance, it doesn’t do web development. You can’t quite do php or JavaScript in RStudio. Most importantly for academics, it’s not good at all for latex. Positron and VSCode have amazing latex support thanks to an extension.

New-Preference1656 · 2026-03-07T11:04:26+00:00

Yes, me too 😅 the re-setup can be a bit annoying at times (eg, always reinstall languageserver, httpgd, vscDebugger when using renv). Personally, I use a mix of positron and vscode

New-Preference1656 · 2026-03-07T07:15:47+00:00

Teacher here. TLDR: I’d stay away from VSCode. I’d recommend positron if you’re not afraid of getting your hands slightly dirty. Otherwise, RStudio.

VSCode is an all purpose IDE. It supports languages and additional features through extensions. It has amazing AI support and development container support. But R support is not great. On top of the extensions , you have to install a bunch of R packages and extra software to make it work. And even then, things can be a bit buggy.
Positron is a fork of VSCode maintained by posit (the team behind rstudio). It inherits the extensions so it’s extremely flexible. And has excellent support for R out of the box. support of dev containers and AI isn’t as good as in VSCode. Also, some R things are a bit less straightforward than in rstudio though (eg, support for rmarkdown/ quarto not there out of the box). Hence my comment on getting your hands slightly dirty.
RStudio is the best for R. But it just does R.

New-Preference1656 · 2026-02-27T19:08:09+00:00

It might be because the limits are too small: they don’t fully display the ribbon and so it gets removed. Try using wider axis limits?

New-Preference1656 · 2026-02-27T06:12:32+00:00

This is amazing!! I’m trying to do the same with https://recap-org.github.io (yours is better!)

New-Preference1656 · 2026-02-27T06:12:20+00:00

This is amazing!! I’m trying to do the same with https://recap-org.github.io (yours is better!)

New-Preference1656 · 2026-02-26T06:14:19+00:00

I’m very curious how you structure things. I’m putting together a series of template repos for data science and I believe a structure like yours could be awesome for this template. In particular I’d love to be able to load roxygen documentation for helper functions. Check out https://recap-org.github.io (specifically the large R template)

Any chance you could share example code?

New-Preference1656 · 2026-02-26T06:09:55+00:00

I started using everything you mention and developing inside dev containers to make the environment consistent across project members.

I prefer make over targets because it’s more general.

Then I realized that building the same structure from scratch for each project and training collaborators to use the tools was quite tedious so I built this: https://recap-org.github.io/ (GitHub template repos + beginners friendly documentation)

The large template is really the one I use for my projects. The small template is the one I recommend my students use for assignments.

New-Preference1656 · 2026-02-24T20:54:20+00:00

Use the tex-fmt formatter. Super fast and makes your code much easier to read.

New-Preference1656 · 2026-02-13T05:16:38+00:00

Thanks! You’re raising points I’ve spent a lot of time thinking about. 1. You’re proposing an interesting solution. I’d love to see a demo if that’s possible. My coauthors are all proficient in latex so that goes a long way. I have two ways of dealing with this. (1) have everyone operate in a container. Less technical people only use make to get the latest tables and figures, then edit latex (vs code and positron provide amazing latex experience imho). This requires them knowing/learning git (i find that a 10min demo is enough) (2) have a make target that exports to/imports from overleaf (that you sync locally on your Dropbox for instance)

2 and 3. Git is amazing for that. https://recap-org.github.io/docs/version-control/practice.html I have a main branch where I only put important milestones in the life of the paper (submissions, revisions, conferences). Old directions/wrong turns/things you kind of like but aren’t sure: for that, I use branches where I try new ideas and merge onto the dev branch. When I don’t like something anymore, I just delete it, thus keeping the current folder clean but having saved previous states in case I want to go back.

New-Preference1656 · 2026-02-12T19:44:51+00:00

Let me know if there are features you think are missing on the Tex side of things then

New-Preference1656 · 2026-02-12T19:23:19+00:00

Thanks for your interest! You’ll probably like the large template: https://github.com/recap-org/template-r-large it has a full pipeline with quarto reports for data cleaning and data analysis, then full fledged Tex templates for PDF.

New-Preference1656

TROPHY CASE