how to know workspace id/name with Xmonad - xmonad

I moved to Xmonad, which is a great tiling desktop manager.
Usually I launch many workspaces with Xmonad.
I often have some troubles to switch the workspace I would like to use.
please let me know how to show the workspace ID/number on Xmonad.

Xmonad itself doesn't provide any visual indication of the workspaces.
However, it provides information about the workspaces which can be displayed by using the statusbars xmobar or dzen.
The module DynamicLog offers some possibilities how this information is formatted.
If you don't know about yet, check out the xmonad contribs, which implement many cool layouts and functionality plain xmonad doesn't provide - the DynamicLog module is one of them.

Related

More than Workspaces : multiple x-sessions?

I am currently working on multiple projects and may do so for several months. I aim to setup my computer differently in order to be more efficient. Currently, I use Ubuntu 22 with mostly default settings. For simplicity, let us assume the main apps I use are:
Firefox
VSCode
Guake (for all that is terminal related)
What I would like, is a setup where I can switch between projects easily (for example by using SUPER + ProjectNumber) and when I am within a project almost everything acts as though it was unaware of the other projects. Mainly:
I only see the apps that are open within the project, whether it is using ALT+TAB, the gnome app drawer, ...
Firefox has only one window instance per project with only the tabs that were open from that project. Opening a second window in the same project opens a new tab instead. This should also be true for other apps that usually run as "single instance with tabs".
Guake has one instance per project and hopefully bash history is saved differently for each project...
There is probably nothing particular to do with VSCode: I can open a VSCode window in each project.
Features 1 and 2 are probably the most important to me. It feels I can achieve feature 1) using workspaces, but not feature 2). Maybe the solution is creating multiple x-sessions? But I really have no idea and I was wondering if there was a common/easy solution to my problem (I feel like there should be, this seems like a rather common pattern). I am also open to other setup suggestions.

How can my application assign a keyboard shortcut in the system from Flatpak?

I am the developer of Planner and I am having a problem assigning a keyboard shortcut to the current system.
Planner is a task manager and has a built-in application called Quick Add that through a keyboard shortcut that can be run regardless of whether Planner is running.
To install this keyboard shortcut I use the following service.
This works perfectly if I build Planner from the repository. However, I have an error if I execute the same function if I build Planner from Flatpak
** (com.github.alainm23.planner:2): WARNING **: 15:54:36.510: CustomShortcutSettings.vala:28: Schema "org.gnome.settings-daemon.plugins.media-keys" is not installed on your system.
I know that I can't access the scheme of org.gnome.settings-daemon.plugins.media-key And I need a hole to edit the dfcon configuration of the system.
The question is how can I do that. If anyone could help me I would be very grateful.
Flatpak by default doesn't allow editing GSettings in a way that affects the rest of the desktop, since rouge applications could use that ability to do things with security and privacy implications, like set or unset proxy servers.
So it would be best to look into alternative ways to make this possible - perhaps provide people with instructions to set it up manually, or request and/or contribute proper portal support for setting global keyboard shortcuts.
If you still really want to implement this, check the link above for the details on the sandbox hole you need to open to make it work.

Unable to modify some setting in MyEclipse

While working with some projects checked out from Git, we get errors with modifying the project settings in MyEclipse. I am trying to modify the deployment values in my workspace and it is not letting me (screenshot below).
There isn't a lot of information to go on, here (e.g. what is the version of MyEclipse, what type of project is this, what properties page are you switching from, the OS and version, whether this has worked before, the error log - but please don't paste that in here - and so on).
However, here are some actions that might help resolve it:
Firstly, try a fresh empty workspace then import the project from the old workspace, or better still import again from Git. This would help clean up possibly corrupted settings in the workspace.
Another thing to try is to launch MyEclipse with the -clean option (just add that option to the top of your myeclipse.ini file, found in the installation folder).
#Howlger is right, though, this is a commercial product and we may be better able to help if you raised the issue in the MyEclipse support forums.

How to set global preferences for eclipse in multiuser environment?

We will be using eclipse(Helios or Indigo) for multiuser environment for development. For this we are working on configuring the eclipse. We have installed the plug-ins Rational Clearcase MVFS Support and Rational Clearcase SCM Adapter.
The users must enable the Rational Clearcase MVFS Support option and the Clearcase SCM Adapter auto-connection option once per workspace through preferences.
So my requirement, is there any way to set these preferences(or options) only one time globally so that everyone automatically gets those settings while creating their workspaces ?
If not this, is there any another way to achieve my requirement?
Appreciate your answers. Thanks in advance !!
Check out Workspace Mechanic. It says you can use it to "Create a consistent environment among groups as large as the entire company, your local team, or even among your own many workspaces"

Is it possible for a team to use Eclipse installed on a shared network drive?

Our lead programmer likes to install tools on a shared network drive to minimize effort when updating. He recently installed Eclipse to the network drive, but when I run it, I get a window that says Workspace in use or cannot be created, choose a different one. After clicking OK, I get a window that gives me a drop down menu with only one item, the workspace on his machine. I can then browse to the workspace on my machine, click OK, and Eclipse continues to start up and run just fine. There's a check box in that second window that says Use this workspace as the default that I've checked after browsing and selecting my workspace, but the next time I start up Eclipse, it reverts back to the lead's workspace.
Are we violating some assumption that Eclipse makes about the install? We're on a Linux network, if it makes a difference.
Setup the shared eclipse such that it can not be modified by the users accessing it. This should (if I recall correctly) force eclipse into a "Shared User, Hands Off" mode and default to storing settings per user account.
Do not share Workspaces (or Projects) -- this will only break things horribly -- use a different strategy such as a proper revision control system.
Perhaps this documentation will be helpful.
"""The set up for this [shared] scenario requires making the install area read-only for regular users. When users start Eclipse, this causes the configuration area to automatically default to a directory under the user home dir. If this measure is not taken, all users will end up using the same location for their configuration area, which is not supported."""
I would try to run Eclipse locally as well as over the network. Using a shared network drive may make Eclipse more painful than it sometimes is. A development environment should work for the developer, even at the expense of a slightly more complicated setup.
Eclipse stores a lot of settings, including the workspace list, in it's installation directory (especially the "configuration" directory). It's hard to say how well sharing the installation will work, but I wouldn't be surprised if there were a number of issues caused by "fighting" between Eclipse instances running on different developer's workstations.
To fix the particular issue you're having, you could set up a separate startup script that passes your workspace as a command-line argument to Eclipse, bypassing the workspace selection dialog you're seeing.

Resources