Is there a way to run P4 command line from P4V? I understand that it can be done MS command prompt. But want to know, if it can be invoked via P4v?
Thanks.
Helix sadly removed the input textbox in 2017.3.
Yes, see View > Log and in the bottom you can run p4 commands
Related
By default, command history is stored in ~/.bash_history file.
I want to save the history for a specific command elsewhere than ~/.bash_history every time the command is called, like in a file ~/.specific-command-history.
I don't want to run grep to search for a specific command neither exclude it from ~/.bash_history, I just wanted to have a history for a specific command to be automatically stored in other file as well as in ~/.bash_history.
Any thoughts about that?
You could create and run an anacron script, even if at a set time the server was switched off, when the server is switched on, anacron will run the script.
The anacron script would grep the file with the command you are looking for, and then use cut, and then append the file you would like to paste the lines into.
I use perforce as source code repository. p4 change command is used to create a changelist of opened files. If I set setenv EDITOR gvim and then run this command then gvim opens and I add some description and then save and quit. I get below error. Same error does not come if EDITOR is not set, I mean in that case vim opens. Any idea to fix this issue?
sachina#inn-sachina-vm[285] p4 change
Error in change specification.
Error detected at line 29.
Change description missing. You must enter one.
Hit return to continue...
Applications that invoke EDITOR assume that the command blocks until editing is done and the editor was closed. While true for vim, the GUI version gvim launches in the background; i.e. the command returns immediately.
You can avoid this via the :help -f command-line option:
setenv EDITOR 'gvim -f'
I am trying to open the diff command from the command line to see the differences between a file and its previous version. According to the docs i can be done with the diff argument. This would give me the difference between a file and the base revision, but did not work for me:
https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-automation.html
call TortoiseProc.exe /command:diff /path:%CD%\%1
To clarify, any one would know how to start from command line the "TortoiseSVN" that would be the equivalent of this:
try this:
call TortoiseProc.exe /command:prevdiff /path:%CD%\%1
you can find the commands very easily:
open the TortoiseSVN settings dialog, go to Advanced. Find the Debug option, set it to true and click Apply or OK.
Now every command you do with TortoiseSVN will first show a dialog with the command line TortoiseProc.exe was started with. That way you can easily figure out the command line you want.
After that, open the settings dialog again and set the Debug option back to false.
Hi I add a new user in my linux mint. But after login that user, some feature losted in the terminal. Such as I cannot use up-arrow and down-arrow in the keyborad to show the previous command. Also there is no color in for different file. Someone could tell me the way to configure these setting? or some link. Thanks
The bash history is user-dependent. You can change the bash settings in the .bashrc file in your home directory, or you can tweak the file /etc/bash.bashrc.
I have had several Debian servers and always edited cronjobs in this way:
crontab -e
and
Ctrl+x
Just got a new server and can not do it in this way anymore.
When I enter crontab -e, the file opens but I can't write anything. I can move cursor up and down but can't write. I even can not exit from this file because Ctr+x doesn't work.
When I open a file there is some information and the rest empty lines contain tildes ~ in the beginning of each line.
Any ideas how can I edit this file?
Thanks.
You need to turn on insert mode. After entering crontab -e, press i to turn on insert, enter your full line, press esc to finish entering, and then hold down shift and press z twice to save the file. This is how I managed to do it in vi/vim
As one other person has suggested, vim is obviously the default editor on your new server. You can test this by running
EDITOR=pico crontab -e
Substituting whatever is your actual preferred editor (sounds like it may be nano or pico). If that works, you should try one of the following:
edit your login script to set that environment variable on login (sets the editor just for that user)
Make sure your favourite editor is is installed and run the following (as root): update-alternatives --config sensible-editor
You can then choose the default editor for all users (they can override it individually by doing option 1).
~ would suggest that you are now editing your crontab using vi/vim instead of your usual editor
so Ctrl-X wont work, try Esc :wq
Do you have the right permissions? maybe you should open it as root user if not.
check it doing this:
ls -all $(which crontab)
if not you can change them..take a look here too..maybe you find something more!
hope it helps.