I using xmonad+xmobar on my computer. I am missing notification on the status bar. May'be was way to integrate it's or ready plugin for this. Any ideas?
The easiest thing is to deploy a system tray in the status bar.
You may use one of these:
trayer: https://github.com/sargon/trayer-srg
stalonetray: http://stalonetray.sourceforge.net/
...
Related
I want to pop up an alert when someone tries to check out a project/file that is already checked out by someone else on TFS, Visual Studio 2012.
Let's say I checked out a file and let others to check out but prevent from check in. When someone else tried to check out same file, pop up should inform them about my checkout, but they can still checkout and try some changes. I searched the web but couldn't find a solution for that.
I know we can look for current checkouts form VS console with tf status command, but I'm looking for something visual when they tried to check out.
One way to achieve this is to use a version control system such as Git or TFS (Team Foundation Server) that supports file locking. In TFS, you can use the "tf lock" command to lock a file so that only you can check it out. When someone else tries to check out the locked file, they will receive an error message telling them that the file is locked.
Another way is to create a script or program that periodically checks the status of the files in the repository and displays a pop-up message if a file is already checked out by someone else. This script can be run on the client side as a background process or on the server side as a service.
You can use the TFS API to check for check-out status and trigger the alert accordingly.
It's also worth noting that some integrated development environments (IDEs) such as Visual Studio have built-in functionality for displaying file lock status, so you may want to check if the functionality is available in your chosen IDE before implementing a custom solution.
Prevent Shutdown on Windows almost using windows API ShutdownBlockReasonCreate when application received "shutdown signal" ,windows message is 17 (need set AutoEndTasks registry key to 0)
simple test with Notepad,if shutdown from start menu shutdown button,Notepad will prevents it.
but if using real power button,windows can not show any prevent UI.
I tested with my application, "close" messages can received ,but can't show prevent UI.
So this is a windows bug or need some special setting on windows?
at last I found a solution. just need use gpedit.msc Go to “Computer Configuration” >manage template>system>shutdown opption set the only one setting to enable (sorry Chinese literal translation xD)
While trying to get GitLab Kanban Board to run nicely with my GitLab server I somehow managed to get myself locked out of the latter. Whenever I open the GitLab-URL now there's the message "No authentication methods configured" and no option for logging in.
Unfortunately, I don't even remember the exact settings that I was messing around with at that time, because it was a while ago and it's only now that I found the time for dealing with this problem again. IIRC one of the last things I did was to try and get OAuth working. (And I think that I was changing some settings in the web interface last, not in the settings files.)
Unable to find a solution online, one of the things I tried was to do a backup and then restore that on a different server. But the result is that I then get the same message on the new server also.
Does anyone have any idea on how to recover from this situation? Is there any way for example to enable "normal" login again by changing settings in the database?
If it's not (easily) possible to recover the whole GitLab installation, is there some way to somehow at least extract the bug report data from it? That's the data that I would be most unhappy to loose...
I'd really appreciate any help, because I'm completely at a loss right now!
You can use the Rails console to reenable your sign-in.
sudo gitlab-rails console
s = ApplicationSetting.find_by(signin_enabled: false)
s.signin_enabled = true
s.save
This will modify the rails settings directly.
As of version 10.5.X, use this instead (different ApplicationSetting key)
sudo gitlab-rails console
s = ApplicationSetting.find_by(password_authentication_enabled_for_web: false)
s.password_authentication_enabled_for_web = true
s.save
I recently installed GitLab to try it out and I am really enjoying it. It's very easy to install and use, still, I found an annoying "problem". I haven't yet found a way to delete Issues associated to projects.
I know that it's not a good practice to remove Issues from the system, but there are some specific occasions where this is really useful, such as when you create an Issue that makes no sense and don't want to be in the system, even after being closed.
So, my question, really simple: Is it possible to delete Issues on GitLab? If so, how can I do it?
I am using GitLab 7.2.1, on Debian wheezy.
Many thanks
It is now possible to delete issues starting with GitLab 8.6:
GitLab 8.6 released with Deploy to Kubernetes and Subscribe to Label
Delete Issues
Sometimes, simply closing an issue or merge request is not sufficient. For those times, we are now making it possible to delete issues and merge requests.
Only owners can delete issues by editing the issue or merge request and clicking, you guessed it, Delete.
At the time this question was asked, No. There is a feature request for that at: https://gitlab.com/gitlab-org/gitlab-ce/issues/2489
Now it seems possible: https://stackoverflow.com/a/36172116/895245
Click the Edit button (Pencil icon for editing the text of the issue)
Below and to the right of the text box where you can enter the description is a big red Delete button. Click it and confirm.
Personally, I find the hiding of a Delete button behind the Edit button and right next to a pretty unrelated Cancel button to be very unintuitive and weird.
You cannot do that any more.
Delete existing issue (Deprecated)
The function is deprecated and returns a 405 Method Not Allowed error
if called. An issue gets now closed and is done by calling PUT
/projects/:id/issues/:issue_id with parameter closed set to 1.
DELETE /projects/:id/issues/:issue_id
Parameters:
id (required) - The project ID
issue_id (required) - The ID of the
issue
Ref: GitLab Documentation
You can do that, but have to modify the database manually. If you have a backup, you can give it a try.
Update: Possible since GitLab 8.6.
I want to launch the browser in a different process when a particular link is clicked on the page. When I checked the net I found the following tip: http://www.dslreports.com/faq/3849 . But there we have to change the registry. Is there any simple way of doing this without touching the registry?
If you use the Google Chrome browser, each new window or tab runs in a separate process. Internet Explorer version 8 will do the same (it's currently in the second beta round).
Earlier versions of IE will run a new window in a separate process if it is launched from, say, the Start menu or the command line, or a link in an email (but not by clicking a link within IE). I imagine you could create a proxy that the client would run through, which would intercept the links you care about and launch them by running a command line request. That seems like more trouble than mucking with the registry though (assuming that registry change still works -- looks like your link is from 2002).
I don't believe this is possible unless you change the client computer setup or software it's running.
Why do you want to do this?