teiI18N.xpr is making me go grrr... (possibly just an oXygen issue)

[bansp]

[edit, Dec 2nd: please see the oXygen forum post linked from the 3rd comment, for now]

(Can't say since when this is an issue, because I've had a break in editing the P5 source, but it seems to me that the pain may be shared by others.)

In essence: is there a chance to add *.xpr to .gitignore, please?

Whenever I open a project in oXygen that has to do with the TEI source, the editor apparently automatically searches the tree for project files, and puts me in TEI/I18N/examples-zh-tw/teiI18N.xpr. It's not the best way to start a productive session in a relaxed state ;-)

Now, probably, there is some option in oXygen that switches off the scan (not sure, just a guess). But I believe that there is a better, systemic approach: gitignore all project files. That should not affect those who use the file in question, but it should provide some relief to those like myself.

Thanks for considering this.

[bansp]

I can see that the .gitignore was last modified 3 yrs ago, and that it contains *.xpr. So it looks like it is my instance that somehow doesn't want to take that into account. I'll see if I can make that go away and will post here, maybe that might be useful for others in my situation, if there are any (the desktop I work on is a bit ancient, so it can be that my repository is much older than 3 yrs and that it needs to be made aware of the 'modified' .gitignore). Oh well, searching for a clue or enchantment...

[bansp]

I have done some testing and it looks like the git add-on plays some role in this.
I've posted an issue report in the oXygen forum: https://www.oxygenxml.com/forum/common-problems/topic27106.html

[ebeshero]

@bansp Yikes, that is an old oXygen project file, and I'm a little shocked that it made it past our .gitignore.
In case this is helpful, I've seen similar troubles on other projects, such that I managed to push something like the .xpr (an .idea directory in my case), and somehow didn't have it listed in the .gitignore or somehow it escaped a newly established .gitignore and was pushed (grrr). There's a quick remedy for this, to remove the files from git's tracking (without removing them from your local system). I think this may work in your case as well:

https://gist.github.com/joshuaquek/221e988df929610ae9568a3b73e7176a

[bansp]

Thanks, Elisa. I was tempted to solve it by some sort of brute force, but then realised that the issue would just most probably recur, at maybe some inconvenient point, for me or others, so I got interested in a 'systemic' solution. Because that project file was never a problem until recently, and I don't think any longer that the .gitignore is the issue (I guess I should modify the title of this ticket) but rather some new interaction between oXygen and the git add-on. I wonder what the developers are going to say.

[bansp]

Okie, not a TEI issue at all.

Alex Jitianu writes:

Yes, it is related with the Git Client. I'm sorry for the inconvenience, it is a behavior that we thought to help people, but it appears to do more harm in this particular scenario. Fortunately, it can be disabled: please go to Options->Preferences... on page Plugins / Git Client and:

• select "Never switch to the new working copy" on the "When detecting a Git repository inside a newly opened projects"
• unselect "Detect open Oxygen projects (.xpr) from opened repositories"

[bansp]

I wonder, @ebeshero -- is this ticket worth leaving open for a while in case others get the issue, having switched to the very fresh oXygen 27.x?