Pinned Git Bash shortcut does not execute .profile #167
Comments
|
Hmm. Essentially the problem is that what you try to pin to the dock is not the Quite honestly, I have no idea how to pin the |
|
because git-bash.exe is just a wrapper. |
No, we cannot abduct @fracz I wonder whether pinning works if you choose the |
|
why not drag&drop git-bash.exe onto the taskbar? This will pin the wrapper correctly instead of the executed shell. |
|
Yes, but you will have two items in taskbar after launching it (the first one for the shortcut and the second for running process). |
|
Here I have the same environment (windows 7 SP1 - 64 bit), but it works nice. When I select Clicking on it the terminal (mintty) is started correctly executing I suppose you gave a look at Finally I suggest to use CCleaner utility, cleaning an old setup. |
|
I have resolved this isse as follows:
|
|
For future record: I could imagine that setting the |
|
@rcdailey feel free to work on the |
…g around octopus merges The commit message below describes the bug. This has been sent upstream hopefully in time for v2.23.0. If we are taking 2.23.0 soon, then we would not need this fix. The question for @jrbriggs and others is: do we rush this fix to the version of microsoft/vfsforgit in EA? There are possible reasons that this is an edge-case enough to ignore: 1. It only affects the split commit-graph when a non-base file has an octopus merge commit. Only one octopus merge exists in the OS repo right now. 2. It will not _break_ users, but will cause "warning: commit-graph chain does not match" warnings and cause increasing performance issues as the base commit-graph files far further and further behind. I'm open to all options here. Thanks, -Stolee --- In 1771be9 "commit-graph: merge commit-graph chains" (2019-06-18), the method sort_and_scan_merged_commits() was added to merge the commit lists of two commit-graph files in the incremental format. Unfortunately, there was an off-by-one error in that method around incrementing num_extra_edges, which leads to an incorrect offset for the base graph chunk. When we store an octopus merge in the commit-graph file, we store the first parent in the normal place, but use the second parent position to point into the "extra edges" chunk where the remaining parents exist. This means we should be adding "num_parents - 1" edges to this list, not "num_parents - 2". That is the basic error. The reason this was not caught in the test suite is more subtle. In 5324-split-commit-graph.sh, we test creating an octopus merge and adding it to the tip of a commit-graph chain, then verify the result. This _should_ have caught the problem, except that when we load the commit-graph files we were overly careful to not fail when the commit-graph chain does not match. This care was on purpose to avoid race conditions as one process reads the chain and another process modifies it. In such a case, the reading process outputs the following message to stderr: warning: commit-graph chain does not match These warnings are output in the test suite, but ignored. By checking the stderr of `git commit-graph verify` to include the expected progress output, it will now catch this error. Signed-off-by: Derrick Stolee <[email protected]>
I have configured few items in my
~/.profilefile (like ssh-agent, aliases, $PS1 etc). Running Windows 7.When I open new Git Bash, on taskbar it is visible with nice color git bash icon (like this: https://git-for-windows.github.io/favicon.ico).
When I right click it and select "Pin to taskbar", it seems to be pinned correctly but the icon is changed to console-like (sth like http://mricons.com/uploads/icon_sets/67/icons/111545/thumb/64x64.png).
When I close Git Bash and open it again from the pinned taskbar shortcut, it does not execute my
~/.profileand the command line looks likeI have to go back to Start Menu -> Git Bash to have my settings executed.\
EDIT:
After executing
in the "pinned command line" I get my environment set.
How to execute it automatically?
The text was updated successfully, but these errors were encountered: