TODO list feature #50

darltrash commented 2026年03月06日 16:57:22 +01:00

It could be pretty awesome if there was something like a TODO list feature built into the editor itself, I think this was proposed for Zed itself but they never added it in the end.

It could be pretty awesome if there was something like a TODO list feature built into the editor itself, I think this was proposed for Zed itself but they never added it in the end.

adrian-brady commented 2026年03月18日 14:47:28 +01:00

I imagine this wouldn't be insanely hard to implement. There's data that is saved alongside a project so I could perhaps use that as a base for implementation.

Should these TODOs be app-wide or project specific?

I imagine this wouldn't be insanely hard to implement. There's data that is saved alongside a project so I could perhaps use that as a base for implementation. Should these TODOs be app-wide or project specific?

ItsHarper commented 2026年03月19日 04:58:50 +01:00

I like the JetBrains implementation of this, where it lets you navigate all of the TODO comments in your codebase.

I like the JetBrains implementation of this, where it lets you navigate all of the TODO comments in your codebase.

ItsHarper commented 2026年03月20日 03:54:26 +01:00

The other component of that is that TODOs get special highlighting in the editor, which I very much miss when using Zed/Gram.

The other component of that is that TODOs get special highlighting in the editor, which I very much miss when using Zed/Gram.

darltrash commented 2026年03月25日 01:24:25 +01:00

@adrian-brady wrote in #50 (comment):

I imagine this wouldn't be insanely hard to implement. There's data that is saved alongside a project so I could perhaps use that as a base for implementation.

Should these TODOs be app-wide or project specific?

Workspace-specific should be good enough in my opinion, since you can just add several folders into your workspace. I am looking at it from the perspective of someone engineering a frontend and a backend at the same time under the same "workspace"

@adrian-brady wrote in https://codeberg.org/GramEditor/gram/issues/50#issuecomment-11783310: > I imagine this wouldn't be insanely hard to implement. There's data that is saved alongside a project so I could perhaps use that as a base for implementation. > > Should these TODOs be app-wide or project specific? Workspace-specific should be good enough in my opinion, since you can just add several folders into your workspace. I am looking at it from the perspective of someone engineering a frontend and a backend at the same time under the same "workspace"

krig commented 2026年05月14日 23:03:22 +02:00

Hello,

I've decided to go through and close issues that I don't intend to fix. If it's a feature request for something that I haven't planned to do, then I would encourage you as the reader to fix it yourself! It's open source, I'm guessing most people who are using a code editor are coders, and it's good for you to learn new things. I've come to realize that I can't fix WGPU issues on a particular piece of hardware for example. Whoever has that problem will have to solve it so they can verify that the fix actually works.

If it's a packaging thing, like providing packages for a particular OS, Linux distro or architecture, then all I can say is that I have tried and there just isn't enough time in my life to support everything people want. What I have done is hook up this repo to a Github mirror with actions enabled: https://github.com/GramEditor/gram. My suggestion to anyone who needs or wants a particular build is to make a PR that adds build support that way.

Hello, I've decided to go through and close issues that I don't intend to fix. If it's a feature request for something that I haven't planned to do, then I would encourage you as the reader to fix it yourself! It's open source, I'm guessing most people who are using a code editor are coders, and it's good for you to learn new things. I've come to realize that I can't fix WGPU issues on a particular piece of hardware for example. Whoever has that problem will have to solve it so they can verify that the fix actually works. If it's a packaging thing, like providing packages for a particular OS, Linux distro or architecture, then all I can say is that I have tried and there just isn't enough time in my life to support everything people want. What I _have_ done is hook up this repo to a Github mirror with actions enabled: https://github.com/GramEditor/gram. My suggestion to anyone who needs or wants a particular build is to make a PR that adds build support that way.