Proposal: Enable GitHub Discussions for questions and workflow discussions

@luccahuguet

Yazelix diagnostics

No response

Details

I've been exploring Nova since yesterday and really like it!

While getting familiar with it, I've encountered a few things where I didn't fully understand the reasoning behind certain design decisions. It got me wondering how you, @luccahuguet, and other users approach your workflows and use Nova day to day.

As I don't want to clutter Issues in this repo and couldn't find a Discord or similar channel I was wondering if you ever considered enabling Discussions in this repo? It could also be a good place to showcase themes and setups, share configurations and how users extended Yazelix.
It could also over time become a searchable knowledge base, supplementing the docs.

I'd also be happy to help keep Discussions organized, identify duplicates, and point people toward existing answers or documentation. I'm still learning Nova myself, so I wouldn't be much help with technical support yet, but I'd be glad to contribute in that capacity if it would make maintaining a Discussions section easier.

Of course, I understand if you'd prefer to keep things centralized in Issues or another channel.

@luccahuguet

are you sure they are not enabled?

it could be after nova migrated to a organizations instead of under @luccahuguet

@luccahuguet

While getting familiar with it, I've encountered a few things where I didn't fully understand the reasoning behind certain design decisions. It got me wondering how you, @luccahuguet, and other users approach your workflows and use Nova day to day.

i'd love to hear all about it, ill investigate if discussions are disabled, but you can open a discussions issue in the meanwhile

I'd also be happy to help keep Discussions organized, identify duplicates, and point people toward existing answers or documentation. I'm still learning Nova myself, so I wouldn't be much help with technical support yet, but I'd be glad to contribute in that capacity if it would make maintaining a Discussions section easier.

awesome, that's very helpful

Apparently I'm blind... sorry!

4.
Apparently I'm blind... sorry!

no worries! you can repent filling issues whenever something is not working, especially on macos 😉

5. > 4.
> Apparently I'm blind... sorry!

no worries! you can repent filling issues whenever something is not working, especially on macos 😉

Deal 🤝

Im curious about your feedback tho!

It's less feedback and more workflow questions as I suspect that my mental model is slightly off:

How are you handling persistent vs. temporary sessions? For persistent ones naming them is obvious but with temporary or "throw-away" sessions you gather these randomly named sessions that are just piling up. Are you just avoiding them by having named sessions for basically everything?
I've noticed that Zellij states that that sessions that were quit and resurrected are not guaranteed to be restored exactly yet CTRL + Q is much easier to hit than CTRL + ALT + O and then D, which suggests to me that quitting is intended to be the more common mechanism to close a session. My intuition was that detaching would be preferable in most cases, especially when you've spent time arranging a workspace.
I don't yet fully understand the intended relationship between the workspace root and terminal panes. For example, after setting a workspace root, creating a new Nushell pane via CTRL + P then N still starts in ~. Is that intentional? I'd intuitively expect new panes to inherit the workspace root, but perhaps I'm misunderstanding its purpose 😆
Is there a particular reason why the pane orchestrator only supports moving panes vertically within a column? When I want to swap panes horizontally I currently switch to the stacked view via ALT + [ or ], then arrange them how I want them via CTRL + ALT + J/K and then switch back again

I'm still figuring out how the different pieces of Nova and Zellij fit together, so some of these questions might just come down to me misunderstanding the intended workflow.

Edit: Just to clarify, this isn't a critique in any way. I hope the points don't come of as hostile!

i dont ever name sessions, I usually just have one session open at a time, and when i need another one, i open a new window and focus on one or the other without session management. I mostly treat them as disposable. and i after some accumulation, i delete the old ones
that makes sense, we should create a issue to track that. also i hate zellij ressurrection, having to say yes to every command, and worst, new tabs become poisoned and they also need you to say yes before the command runs. BUT i actually just checked and that last problem is not present anymore, so zellij ressurrection should be pretty decent now, you just say yes to the commands of the existing panes. we still need a way to save and load layouts tho.
good call. i fixed it yesterday after reading your comment (oops, i fixed only alt m, not ctrl p + n, hey why are you not using alt m???)
ah. good idea. this vertically split layout is new, so i never thought about this. will create a issue.

this type of feedback is immensively helpful, thanks!

@megravity

Thanks again @megravity, this turned into concrete work:

Sessions: no change planned. Feel free to open issues
Quit vs detach: Ctrl q stays as Quit. The underlying wish, keeping an arranged workspace, is really about saving and loading layouts, so it's now part of Design user-declared Zellij layout profiles #579.
New panes and the workspace root: Alt m already opens at the tab's workspace root (fixed yesterday). You used Ctrl p then n, which is still Zellij's native new pane and follows the focused pane's directory. The same applies to pane mode's d, r and s and tmux mode's " and %. That's now a bug that blocks Nova 2.0, so all of them will follow the workspace root too.
Moving panes across columns: filed as Move work panes across columns in the split arrangement #708. It needs a key decision, since Ctrl Alt h / Ctrl Alt l currently move tabs.

GitHub Discussions are enabled, so workflow questions like these are welcome there too.

Posted by Claude Opus 5.5 (high) on behalf of @luccahuguet.

Plan the #707 follow-ups: pane-mode workspace root and column moves […

what do you think? anything missing?

Open pane-mode n, d and r at the tab's workspace root

#708 (comment)

9. i dont ever name sessions, I usually just have one session open at a time, and when i need another one, i open a new window and focus on one or the other without session management. I mostly treat them as disposable. and i after some accumulation, i delete the old ones
10. that makes sense, we should create a issue to track that. also i hate zellij ressurrection, having to say yes to every command, and worst, new tabs become poisoned and they also need you to say yes before the command runs. BUT i actually just checked and that last problem is not present anymore, so zellij ressurrection should be pretty decent now, you just say yes to the commands of the existing panes. we still need a way to save and load layouts tho.
11. good call. i fixed it yesterday after reading your comment (oops, i fixed only alt m, not ctrl p + n, hey why are you not using alt m???)
12. ah. good idea. this vertically split layout is new, so i never thought about this. will create a issue.

this type of feedback is immensively helpful, thanks!

Sorry for the late reply. Was traveling yesterday and couldn't reply earlier!
I really appreciate you taking the time, both to answer my questions and misconceptions.

Regarding your feedback:

Makes sense, will definitely try your approach to sessions!
Then I might be experiencing a bug here as I seem to brick Helix when hitting yes after resurrection. But before you do anything, I'll do a quick pass of debugging to see if that's and issue specific to my setup. Will open a separate issue if I can confirm that it's not caused by my local setup!
Good question, alt + m seems much better anyway lol
Thanks a lot for implementing this so quickly!

13. what do you think? anything missing?

You pretty much addressed everything and insanely quickly at that!
This is great!

#708 Is really helpful for my workflow!!

If I can be of any help for #579 let me know 😄

Will try to investigate my resurrection oddities later today!

#709

letting panes move to the 'single pane' on the vertical split was more work than I thought, but all worked out in the end

and i love the final result

Navigation Menu

Repository navigation

Proposal: Enable GitHub Discussions for questions and workflow discussions #707

Yazelix diagnostics

Details

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Proposal: Enable GitHub Discussions for questions and workflow discussions #707

Description

Yazelix diagnostics

Details

Activity

luccahuguet commented on Oct 16, 2026

luccahuguet commented on Oct 16, 2026

luccahuguet commented on Oct 16, 2026

megravity commented on Oct 16, 2026

luccahuguet commented on Oct 16, 2026

megravity commented on Oct 16, 2026

luccahuguet commented on Oct 16, 2026

megravity commented on Oct 16, 2026

luccahuguet commented on Oct 17, 2026

luccahuguet commented on Oct 17, 2026

luccahuguet commented on Oct 17, 2026

luccahuguet commented on Oct 17, 2026

megravity commented on Oct 18, 2026

megravity commented on Oct 18, 2026

luccahuguet commented on Oct 18, 2026

luccahuguet commented on Oct 18, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions