Niri – A scrollable-tiling Wayland compositor(github.com) |
Niri – A scrollable-tiling Wayland compositor(github.com) |
But if I may, I'd like to see just one implementation of a vertical bar where the text is rotated, especially if it's going to display the time. I mean, I want to see it, but not enough to actually DO anything about it.
2) There's something like this for GNOME, albeit not as cool... and this may actually get me to finally install Wayland
3) since I'm on NixOS, if important things break, I can always roll it back
ultimately it turned out that after years of i3/sway scrollable tiling doesn't feel natural at all (and neither do dynamic workspaces, but that's less significant). when i resurrected my desktop a couple of months into the experiment i found it also lagged quite badly on my desktop with an nvidia card (a 3090, tried both drivers) and i couldn't be bothered to figure that one out so that was the final straw and i went back to sway
i was quite impressed with the level of thought that went into the ux and the amount of polish in everything though. it already feels like a serious, well-made piece of software, and it's not even that old yet
I use Omarchy, btw.
I was a former Hyprland user but after I switch to Niri I didn't look back because I think it's kind of having best of two worlds.
In my workflow, I have browser on workspace 1, code editor on 2, CCTV Viewer on 3 (we have a baby and babysitter so I occasionally check them).
In the other monitor, I have slack, terminals etc.
So when I need to switch between browser <-> code (or terminal) I can do quickly. Scrollable comes in handy when you need to check something quickly; for example you are trying to solve something and you need to run some commands in terminal. In that case I just open a new terminal next to browser, do my job and get rid of it.
Also the Super+Tab view is awesome, you can easily see which window is where. Niri also some IPC features so you can find window id and make Niri focus to it. This comes handy if you use Vicinae (Raycast like launcher for Linux). I can switch windows with just using that.
One final note, I highly recommend DankMaterialShell - https://github.com/AvengeMedia/DankMaterialShell/ along with Niri.
DMS looks pretty slick.
I've been thinking about this comment all day trying to decide if this was an unironic "I use Arch btw" or an intentional homage, but it made me laugh a lot
But Omarchy is a fully pre-configured distro, there's no flex in that.
Sure, I think if you disagree with the majority, you'd go Arch and rice your own from the base install (lot of folks who do), but if not, it's a very streamlined way to get off to the races with a community supporting the shared baseline 'opinions'
Must we leave the vicinity of people we don't always agree with?
[0] https://github.com/noctalia-dev/noctalia-shell [1] https://github.com/AvengeMedia/DankMaterialShell
"You can also run niri inside an existing desktop session. Then it will open as a window, where you can give it a try. Note that this windowed mode is mainly meant for development, so it is a bit buggy (in particular, there are issues with hotkeys)."
IIRC in this case the Mod key is by default Alt instead of Super.
Also: - Rust - Great Nix Flake (thx Sodiboo) - Wayland
I'm using Regolith, which is installed in two commands.
Oh maybe it's just up and down
I suppose if it's built like top-left is 0,0 you could just scroll up/left to get to the beginning
If you imagine there are 4 windows and are arranged 2x2 then I was thinking you'd have an icon somewhere like
[ ] [*]
[ ] [ ]
So you'd know you're at the top right position
So it's a but ridiculous imho, there's no flex in it but you try to flex anyways...
Maybe the video of the overview on this page will help: https://github.com/YaLTeR/niri/wiki/Overview
This does have the dots (vertical position) on the right bar
Long as the windows stay fixed, it annoys me how Mac will just randomly re-arrange your virtual desktops or whatever you call em
I use i3 personally at this time regarding this topic but yeah although I used to only care about it because I had crappy computers at the time so not having a full desktop meant saving 400 MB of RAM at idle for example
Being able to have an unlimited number of windows on a desktop (without continually switching the tiling structure) makes them collections of topics rather than having multiple desktops bounded by what fits comfortably. What used to be a switch from the "editor and terminals" desktop to the "browser" desktop is now horizontal movement on the current desktop to the related browser window (general browsing is on a different desktop).
Really low barrier to entry, works great out of the box. There were some wayland teething issues (application support, e.g., no Zoom), but nothing that couldn't be overcome (occasionally by falling back to X). Most of those have been resolved with time.
Edits: Hardware: 2017 System76 Bonobo WS, 2x GTX 1080, multiple screens (4k @ 2x scaling + 2 1080p). PopOS.
I'm running a 1-2 year old build of niri (because it isn't broken), so I've not experienced some of the fancier animations & etc. others dislike.
I consider cloning and building from source to be low barrier to entry if it doesn't involve major setup effort (it doesn't/didn't), so I may be biased. Caveat emptor.
I used to use i3 on a 49" super ultrawide monitor (32:9) and when I did each desktop was truly a topic, with a deep arrangement of windows on it and tabs to switch different areas over to different tasks.
My primary interest in tiling window management is being able to see all of the things that I need to see at once, at once. For me, it's all about context-- placing related windows next to one another. It seems like for others it's about being able to switch between a limited set of fullscreen windows quickly.
I like that Niri gives me a flexible way to divide my workspaces by topic without the windows stealing screen-space from each other. It doesn't feel much like hunting for windows, it feels like... a materialized view of alt+tab. Maybe I have a browser to the right of my editor and a terminal to the left. I can quickly shuffle back and forth between being able to edit while also seeing one or the other.
I even have this binding to cycle the columns to the right of the active window:
Mod+Tab hotkey-overlay-title="Cycle windows to the right" {
spawn "fish" "-c" "niri msg action focus-column-right; niri msg action move-column-to-last; niri msg action focus-window-previous";
}I will say, recent builds have a 'mini map' sort of zoom-out feature that I quite like - my one critique of niri was that I would sometimes get 'lost'.
But in this "endless horizontal tilling" scheme, the above principle would no longer hold, right?
Paperwm on gnome has this.
I didn’t try it myself though. I found it while scrolling https://github.com/Vortriz/awesome-niri
Would you mind going into more detail on what actually happens when you move horizontally? What happens when you have a fullscreen editor, then slide over to a half-screen browser? Do you only see half the editor, or does the editor get squished?
One thing I desperately want is a tiling wm that is also a browser. Like if surf ran a practical engine and was more deeply integrated into dmenu.
Generally I believe most people like to order their workspacesroughly by topic, e.g. all work related Windows on one, browser or on another, some also do all terminals on one... Now with sway/i3 I often found myself in the situation where I was e.g. on the "browser" desktop and you read something you quickly want to try in, e.g. ipython, or you are working on a latex document and want to briefly open a PDF. In i3 that would reduce the size of your original window, so you end up switching to a workspace (or you manually switch to tabbed tiling) for me the mental overhead was significantly higher and I was ending up creating more and more workspaces just to hold temporary terminals.
This is actually related to why I switched to i3 in the first place, I just felt vertical tiling is the only tiling that makes sense in 95% of the cases and that just worked best in i3. But that comes at the cost that you are limited to only 3-4 tiles per workspace (depending on screensize) now in niri I have infinite theoretically. Which means I spend less mental overhead when I want to open another window (which is really thebgoal of tiling wms in my opinion, reduce thinking spend on window management)
If the widths don't add to 1, there are two possible behaviors (configurable). Either the newly focused pane adheres to the size of the screen (e.g., scroll right from the full screen editor and the half-screen browser is on the right border with half the editor visible), or the newly focused pane centers on the screen. I prefer the first behavior, but I make significant use of the "center pane" keybinding.
The Video Demo section in the README gives a pretty good demonstration of this behavior in the first 10-15 seconds.
Edit: To add to this thought and address some comments elsewhere about losing windows, I use "struts", which show P pixels of the panes to the left and right (when they exist) of the current view as a visual aid/reminder of where I am in the ribbon. These reduce the size of the tiled section of the screen and the calculation of pane size accordingly.
I thought of this because it sounds like one of the reasons you're not upgrading it is fearing the risk of it fucking everything up and it being a pain to roll back (your "it ain't broke, so why fix it?" is a hallmark of that mentality). Well...
I will never use another Linux distro for this specific reason. NixOS is the complete freedom to dip in, dip out, roll back on problems, try new things out, etc. The freedom to experiment, try it, back out if there's any issue... but with seatbelts, thanks to the declarative nature of everything (as well as being able to pick previous "instances" on boot).
Afraid of Nix (the language)? LLM's make that trivial these days. For example, I just did something like this today: "Instead of using the one in nixpkgs, whose build has issues on my hardware, set up a derivation that uses its git repo and compiles that instead." A minute later, boom. Declarative working glory, forever.
Of course I also use X11 so this thing would not work for me anyway.
IMO smaller screens are where it shines, but you can also vertically stack within a column in Niri for similar density compared to tiling if you want.
> I keep track of which terminal goes where based on (among others) location.
I think this is a pretty nice benefit of Niri actually, having a second dimension to work with makes it much easier for me to keep track of windows because I can reduce the total number of workspaces and instead rely in part of relative location to other windows without being forced to fit all of them completely on screen. When I don't need my full screen real estate I often set up splits so that a little bit of the offscreen window is still visible and it makes it effortless to remember whats there.
"Normal" tiling WMs / compositors just don't work for me, but the tiling model does. Before niri, I used PaperWM and GNOME -- but a GNOME extension can only do so much. I wish the folks doing COSMIC would add scrollable tiling, but unless/until they do I'll probably stick with niri.
I've been using it for years now and it's obvious that Smithay and Niri are high-quality projects, I haven't had any issues other than missing features (more of which has become available over time).
As a maintainer I'd still want to review PRs myself before merging, no matter how many random people did it before me.
As a contributor, I'd hate for a random with shallow understanding of the problem/project to come in and tell me I had to change stuff or say my PR's no good, in the chance that the maintainer is easily influenced by strong internet opinions.
Linus Torvalds doesn't review all changes he merges, how do you become a comaintainer if not assisting with maintenance?
If you can't review, don't make a PR (or something).
That said, the other big benefit for me is it breaks a lot less often than hyprland and its ecosystem seems to (and I don't just mean bugs here, I also mean things like config file format changes). And this isn't a slam on hyprland - I was only ever mildly annoyed by its breakage.
Nothing really to take out of it except that I feel like I'm not alone feeling stuck, knowing there are better workflows and not being able to do anything about it.
Just the other day the author merged 2 PRs to handle both use cases https://github.com/YaLTeR/niri/pull/2482.
It's not in a release yet but hopefully soon.
Does Wayland actually work now? I've tried it every few years for over a decade now and every time I ran into showstopper bugs (usually on nvidia cards).
Niri feels like it lines up more naturally with the way I tend to use windows and workspaces. I'm working on one project per workspace, opening an occasional ephermeral terminal window or web browser to the right when I need to reference something or run a quick command. My other windows in the workspace aren't altered by these new ones, no reflow happens, and then I can close it when done.
My only problem with Niri is that now I really want an Ultrawide monitor.
Anyway, for that short amount of time I liked most of it on my ultrawide monitor. Except when you open just one application, it stays on the left-most part naturally and it honestly sucks to look at. I have no idea if I could modify the settings to launch apps with an offset and eventually occupy the complete screen estate. I‘m planning to build a new AMD machine and will try Wayland compositors again for a longer period of time. Niri is my first candidate.
With this latest go I gave River, QTile, and Niri a try. After a bit of swapping back and forth, I've settled on Niri and am slowly adding functionality I'm missing.
- I like multiple dynamic workspaces (grouped by function) and don't see much point beyond a split or two so Niri worked pretty well, and I was able to largely config all the keyboard shortcuts to something that made sense to me
- I'm using waybar and swaync for my other DE bits
I've also been using long running Claude Code/Codex in a workspace to build a number of custom scripts:
- niri-workspaces - dynamically generate a workspace display on my waybar showing windows, activity
- niri-workspace-names - integrate w/ fuzzel to let me rename workpaces
- niri-alttab - getting app cycling working in a way that makes sense to me, this is a larger project probably if I want live thumbnails and the like
- niri-terminal-below - I often want to have a new vertical terminal split and it's a bit hacky but works (have to punch out a new terminal, then bring it below, and move back if on the right side)
I haven't gone through all the docs, done much looking around, but one nice thing with these new coding agents is that they can just go and do a passable job to tweak as I want.
https://github.com/dawsers/scroll
niri concept implemented in sway.
I can focus for hours on end and spend zero mental energy on resizing a window. I had less of that with i3wm but you had to always readjust after a few windows were tiled to your workspace. That final bit of cognitive overload was removed with Niri.
EDIT: Spec: RTX 3090, Pop OS 24.04 (beta), 4K 43" Monitor,
Niri Installed from cargo build, super easy install, make sure you install xwayland-satellite so that you can run VS Code, Obsidian, Zoom, Blender and other strictly X11 applications
That being said, these days I prefer floating windows so I just use GNOME.
Maybe a bit more self discipline would help :)
Yes, i know they can usually be deactivated, but it's stupid to have them as default
https://github.com/hyprwm/hyprland-plugins/tree/main/hyprscr...
Imo Hyprland should merge this hyprscrolling plugin into the main project, and just ship it as the default (only?) layout option -- it just scales to "more than 4 windows" so much better than either of Hyprland's master/dwindle layouts.
[1] I tried vanilla arch + archinstall + sway/niri/etc but really couldn't make it work from scratch, vs. the contrast of Omarchy which was "wow this all works" :shrug:
I really want windows to be able to span columns. So if I have 1 column with two windows and focus on the bottom window then create a new window/column to the right, I want that new window to be on the bottom half of column 2. I want the window from the top of column 1 to stretch across columns 1 and 2. If I again create another window/column to the right, that top left window should stretch across columns 1-3. So I should have one very wide window across the top of the screen and 3 windows across the bottom.
I've started playing with this idea in the hyprland hyprscrolling plugin but I'm kind of an idiot and don't have much free time these days.
Ideally, I'd want to set that in a configuration, so if I made adjustments to a window one time it wouldn't change the default sizes.
I usually have VS Code, Terminal, Web Browser and maybe Email, Teams, Discord etc open depending on if it's work or personal. While I can't use this at work (Windows), I may give it a shot on my personal desktop.
It definitely had caught my attention and I might look at it too in the future.
I am really distro hopping and trying out a lot of things recently as I have really cut down on the amount of software to just zen-browser with bitwarden and ublock origin,signal and micro and zed for the most part with some custom zsh script and hyprland cachy had a fish shell which looked gorgeous out of the box and very very similar to my zsh script but my zsh script always had problems with history and what not and it seems that they are fixed now so I am very very happy.
Outside of the fundamental window management differences, I find that a lot of stuff with niri is easier to make work, or just happens to work out of the box. Screen sharing with sway was always a problem for me[1], whereas for niri it works great (incl. sharing individual windows only[2].) I also found that niri is much better at letting hardware go to sleep (which saves 10W on my GPU.)
[1]: https://github.com/swaywm/sway/issues/7898 etc.
[2]: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3864
It is not that I am inexperienced (Windows 95/98/2k/XP/Vista/7/8/10/11, Linux with all kinds of Desktops over the years (KDE 2/3/4/5/6, Gnome 2/3, Sway, Unity, XFCE, Enlightenment, blackbox, ...)), or that I didn't try (searched, watched several YouTube tutorials). I also tried different options, such as disabling the entire "Displays have separate spaces" feature (it fixes some cases, but others worsen).
My verdict is simple: They would be better off just adopting the dumb Microsoft Windows 95 approach to window management.
And it isn't that I don't like the system overall. I have never had a laptop with such superb performance, and at the same time, it stays cool as ice and silent. I love the animated video backgrounds on the lock screen with the slowdown on login, and having Zsh as the default is also fun. But the window management...
What's funny is that when someone first learns about Alt+Tab it's like the best cheat-code for any desktop navigation, but after switching to Niri, Alt+Tab seems like a silly way to layout your windows.
It (the scrolling layout) is not exactly the same as Niri because the implementation is based on my personal preferences, but it does what it's supposed to on both platforms
I’ve had two employers with dumb rules like this and I just worked on a Linux VM running fullscreen on all monitors. It was technically macOS, so IT didn’t have any issues, and it still ran all the security stuff that my employer wanted. At one job, my manager even provisioned a VMWare license for this.
[0] https://www.hammerspoon.org/ [1] https://github.com/mogenson/PaperWM.spoon
It took me about 30 minutes to replicate some Windows/AutoHotKey crap that I wrote myself and have been using for years, and it wasn't painful.
I have tried to get this in KDE Plasma 6 (with a global menu bar) and you just can't quite get there, so you have to settle for maximised but not full-screen apps, which is annoying.
I understand the difference and the architectural history that is that "full-screen" on X/Wayland is essentially a kiosk/don't-interrupt-my-game mode, whereas on the Mac it is chromeless windows on a virtual desktop that you can't get stuck in if you forget the restore keystroke.
But it frustrates me I can't get that.
I genuinely don't get why so many devs use MacOS when Linux is already set up for devs, and the stuff you run in the cloud will also run locally with 1/100 the SSH keyboard latency.
For me cmd+tab / cmd+` works brilianty - switching to last used app/window-of-the-app
Mostly made the switch because Wayland seems to run a lot smoother and efficient, especially when it came to Firefox for some reason.
There are many like this. It mostly works, but it isn't as flawless as just using X11 (unless we are talking about displays and stuff).
Nvidia works since driver 570.
(Edit: grammar and Nvidia note)
What I still miss is stuff like browser docks in OBS and such things that just work in X but are being dragged on for multiple years to be supported on Wayland now (CEF thing though)
Every time I try it, I am really impressed with the smoothness! But every time, two issues come up, which most likely due to NVIDIA, which are complete showstopper.
1. After inactivity period, monitors turns off. When I resume, one monitor won't come back up. I have to deactivate it on control panel, and cancel to get it back. Doing it many times a day, is extremely annoying. This does not happen on two monitors.
2. Monitors won't turn off ... yeah, after inactivity period the monitor's blanks, but, briefly turns off, and then turns back on. And then never turns off. This mostly happens after playing games.
I think both of the issues are due to NVIDIA.
Otherwise, Wayland has become really solid.
Using i3 now, it's not much, it's boring, and that's a good thing.
I can't remember all the bugs, but I've definitely at least encountered all flavors of flickering bugs, stale updates, GPU crashes, failed copy and paste, failed screenshares, failed videoconferences...
From comments on this thread, it sounds like things have drastically improved and its probably time to take another look.
This was on my Bonobo WS (PopOS) w/ 2x NVidia GTX 1080s, multiple screens (2 1080p, 1 4k at 2x scaling), etc. No issues other than app support.
Highly recommend trying it. Very low barrier to entry.
So two external monitors working, except if they are daisy chained I am logged out when (dis)connecting them. So I use one hdmi and one dp over usb-c and it works.
So, not 100% but works better than X for me. Still too recent to have seen all the edge cases though.
I know it doesn't sound all that interesting, but once I used it for a while, I just couldn't go back.
RTX 3090, Pop OS 24.04 (beta), 4K 43" Monitor,
Nvidia cards worked out the box with no problems
I do have some struts on the side, but I'm basically always juggling with at least 4 or 5 tasks so I always have things open; (I'm not using any right now but I do like the "quake terminals" temporary term styles... But for the same reason it's not always appropriate -- if I didn't close the term, it's because I wasn't done with it and mean to get back to it...)
I started using niri before the overview, I think that could help if I get used to it. But better than overview, what I'd want is something always visible like some horizontal scrollbar indicator to remind me there's e.g. more than 3 windows hidden or something. That might be possible to do with waybar and a bit of glue parsing the windows list...
Hmm, perhaps that could be made more interactive and allow cycling through these without closing the search overlay... I'll give that a try! :)
echo "TMOUT=$(units -t '7 days' seconds)" >> .bashrc
My pet-peeve is slow animations, as animations can help my eyes/attention to navigate to/from areas of the screen, but when they're too slow, it's just so damn frustrating that I prefer them off. But smooth, fast (nearly invisible) and clean animations seems to help me navigate better/focus faster than just being eye-candy.
I did change the settings to speed them up significantly, which I think is a good middle ground.
Before Niri I used PaperWM on Gnome with animations disabled and I found that it actually substantially reduces the usability of this sort of workflow for me. I'm not sure how to phrase it, but scrolling WMs feel a little more "physically grounded" and without the animations it was somewhat easy to become briefly disoriented whenever scrolling/opening/resizing/rearranging windows, at least once you start having 4+ workspaces and several screen widths worth of windows on each workspace.
Turning on the animations quickly makes it all snap into place and I never have the brief moment of "feeling lost" after an operation, so it sees inherently important to this WM style. The animations are very fast out of the box and do not feel superfluous.
Maybe there is a point to have them not be a default but that might be a hassle for people like me.
There is a point to be made that maybe cachy and others could opinionate it themselves but the stock shouldn't have animations but if you know that they can be deactivated easily, its definitely a mixed bag of sorts.
Like see neovim, people want to use that software with some saner defaults so they use things like lunarvim / nvchad etc. but even when I was on omarchy (which I stopped after reading https://jakelazaroff.com/words/dhh-is-way-worse-than-i-thoug...) neovim with these mods never really worked with LSP and so many other nice to have features and other things with me (maybe skill issue from my side but there was always one or two errors in that neovim and I just prefer micro nowadays, it just works)
Simply not all people get so easily distracted... It may be signs of mild ADHD.
Can't you? You used to be able to show the tab bar only when there was more than one tab; I guess that has disappeared?
You can do this: Put this code into your userChrome.css file:
#tabbrowser-tabs .tabbrowser-tab:only-of-type, #tabbrowser-tabs .tabbrowser-tab:only-of-type + #tabbrowser-arrowscrollbox-periphery { display: none !important; }
#tabbrowser-tabs, #tabbrowser-arrowscrollbox { min-height: 0 !important; }
Niri also has named workspaces, but when I switched to niri, I realised I only want named workspaces for very few things everything else is just temporary.
I use Niri and it has 3:
1. Use all width (windows are full height by default) and display system bar
2. Use the entire screen and hide the system bar
3. Same as 1 but make the app believe that it’s in Mode 2
Quote:
We're using xwayland-satellite rather than Xwayland directly because X11 is very cursed. xwayland-satellite takes on the bulk of the work dealing with the X11 peculiarities from us, giving niri normal Wayland windows to manage.
xwayland-satellite works well with most applications: Steam, games, Discord, even more exotic things like Ardour with wine Windows VST plugins. However, X11 apps that want to position windows or bars at specific screen coordinates won't behave correctly and will need a nested compositor to run. See sections below for how to do that.
Noting the release notes, it does have many animations already enabled (but I have some or all of them disabled through config).
I'm not recommending anyone run this in favor of newer versions, but it's working for me.
I think that's the beauty of tiling WMs (and I consider scrolling WMs a subset), you can really adjust them to suit your work flow even if work flows might be very different. In contrast stacking WMs seem to be more a lowest common denominator type thing. They work with every workflow, but suboptimal.
Seems like the app decides what the behaviour is. But the point being it's the same behaviour as the Option + Maximize.
Some kind of alert task that would tell you you have window open that you didn't visit in days would probably also be useful to your point.
I am not against it, just I can see positives in this. This is like tmux without tmux.
Things on other desktops are invisible in every WM.
The only difference with niri is the possibility for things to be left or right of the current window. Overview helps with that, but I know what I expect to be on a specific desktop (it's related to the topic) and seldom need it.
Now you want to access that terminal on /tmp/ again. Where was it?
In i3, I just spam-switch workspaces in this case, but at least I can find them. With scrollable wms, every ws can potentially hold that target app.
If you have (having had "Editor" focused, and just opened "TermT"):
Editor | (TermT) | Term | Browser
(FM) | Term | Browser | etc.
The answer (for me) is to think of desktops as topics. The terminal on /tmp is with the things that prompted its creation. If I needed to check some log output, for example, it's with the project that made that log output.
Edit: Note that there's nothing keeping you from stacking those terms if you like, i.e., the appropriate keybinding goes from the previous to
Editor | (TermT), Term | Browser
(FM) | Term | Browser | etc.
Vastly preferable to having to look at the edge of the screen.
You can see window titles on the tabs on the tab bar, but you can’t even see the title of windows which are in a split container of a background tab.
But yes, that wouldn't be true, though focus moves to fresh windows so it's not an issue.
For those on older niri versions I have to say the "zoom out" overview feature is definitely worth the upgrade. As another poster said it really fixes the one issue on scrolling/ tiling wms, which is getting lost.
If you have something that would be reasonable to open on any workspace because it's ephemeral (they used a tmp terminal as an example), and you open it, navigate away from it, and then switch workspaces a few time, and then get pulled into a meeting or go to lunch, and come back, switch workspaces a few more times...
"Where did I leave that terminal, I dont remember where I was when I opened it."
In i3wm/sway etc, you can cycle all your workspaces and eventually one of them will have it visible. On Niri, as you cycle through all your workspaces you may never see it because you don't see all the windows in a workspace, unless you scroll through the workspace panes as you cycle workspaces.
It's not a problem necessarily, but it is something to consider. It sounds like this doesn't affect your workflow, but it might affect others.