The main tig view shows a very useful one-line-per-commit view with the AuthorDate in the first column. Is it possible for this to display the CommitDate instead?
No, Tig only allows to display the date recorded for the author of a commit.
Related
So basically I am trying to rewrite a bash script which uses dialog --radiolist for choosing locale,keyboard,time. At the moment the tag is a number that corresponds to a local (I created a hashtable for it). But because I have, and want to keep it that way for now, around 100 locales it gets messy at the end.
What I wanna achieve is to make it more compact without having to add or add an artificial, non visible item that might easily translate to its tag. (as a tag I would put the locale name)
What I have tried:
1. Noobish thing but I though that there might be some way to include empty like NULL in ASCII or 0, blank space etc, but dialog would always make it visible.
2. Exclude the item at all and finish on on/off but instead on/off takes place of item (not surprisingly if options are as follow --radiolist text height width list-height [ tag item status ])
3. Instead of letting the dialog on exit write to the output the name of the chosen locale I created an output statement myself.
I had red a lot about dialog and whiptail(http://linux.die.net/man/1/dialog, http://linuxcommand.org/lc3_adv_dialog.php) but always end up with having to add tag and an item. Would appreciate any suggestions and maybe some info if there is easily plug-gable dialog/whiptail compatible libs.
Thank You in advance
Perhaps you overlooked the --no-tags option (see manpage):
--no-tags
Some widgets (checklist, inputmenu, radiolist, menu) display a
list with two columns (a "tag" and "description"). The tag is
useful for scripting, but may not help the user. The --no-tags
option (from Xdialog) may be used to suppress the column of tags
from the display. Unlike the --no-items option, this does not
affect the data which is read from the script.
The question mentions whiptail and consistency, which could refer to consistency across dialog and whiptail. There is none, since
whiptail provides fewer options than dialog (inevitably, there will be differences, since there is no one-one mapping possible)
consistency as such between the two is done in dialog occasionally to help with compatibility (the reverse is not true).
If i open up tig with another branch:
tig otherBranch
Is it possible to navigate to the tree view find a file that I want and check it out to my current branch?
Yes, you have to add a user-defined command in ~/.tigrc, for example:
bind generic ^F !?git checkout %(commit) %(file)
Then open tig otherBranch, press t to go to the tree view, navigate to the file and press Ctrl-F.
My problem is this:
Basically if I try to commit a change to SVN and the commit fails then all the files I have selected are lost or forgotten and I have to go back through and choose the ones I want to commit again.
This is hugely annoying and I've not been able to find a solution to it.
So, is there any way that I can get TortoiseSVN to return to the state it was in just prior to when I pressed OK? i.e. all my selected files and comment are restored.
I know I can get the comment back using the Recent Messages button so it would be really handy if I could also do something similar to get the file list state back to what I had too.
For TortoiseSVN 1.6:
Settings-Dialog->Dialogs 2->Reopen commit and branch/tag dialog after a commit failed
in TSVN 1.7, that option is enabled by default, and only available as Settings->Advanced->OutOfDateRetry
If that is something that happens often to you, you could use change lists in TortoiseSVN. It works like that:
You check for modifications in your files by using the menu entry TortoiseSVN > Check for modifications.
In that dialog, you select the files you want to commit together, and select from the context menu Move to change list > <new changelist>.
You enter the name of the change list and accept it.
In you commit dialog, you see now the files grouped by change list, so if anything goes wrong, that information is kept then.
If you change the same files again and again, you may check the check box Keep changelists so that you may use the change list for your next commits.
when I was checking the latest difference in code in SVN Log, accidently I clicked blame differences insted of show differences. Now, when I check the log again I do not see anything visible related to my blaming.
Do you know what exactly happens when you blame a difference? Does it effect the repository and if yes, how can I undo that?
My understanding of blame, is that it shows you who last modified a given line in a given file so you can determine which person to blame for that change. It does not change anything on the server side.
http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.blame.html
In short: blaming shows you, who made which changes were to a file. Ususally the last changes will be shown for a given file for a simple blame report. If you choses to show the blame for a diff of two revisions, you will get the diff of the blame reports for the changes.
But there is no change in the repository.
Take a look at chapter
4.23. Who Changed Which Line?
in the TortoiseSVN help file.
Is it possible in Word 2007 to create a revision history table automatically using track changes or some other method?
e.g.
Revision History
DateVersionDescriptionAuthor
16/09/20081.0CreatedJohn Smith
17/09/20081.1Fixed dumb spelling errorsColin Jones
I don't think it's possible to do automatically.
I'd suggest that you keep track manually with a table like you suggested, and then keep all your documents in a version control system under a separate documentation branch in order to have an automatic revision history. If you feel up to it, you could also create a tool that compares said element to the revision history of the document and shouts at you if you haven't updated it :)
It is really a serendipity as I was grappling with the exact same issue a few days back. Although the approach I used was manual, it was quite intuitive.
There is an option to compare documents in word 2007 in the review tab.You can choose to generate a new document with only the changes. Open the change document on a second moniter and manually incorporate changes.
You can also go to Print and select printing the markup in the new document( if present) but as even the most trivial of changes generate a new entry, it becomes difficult to get to the meat of the changes.
Hope this helps.