Add `change to file relative` and `change to project relative`

Structure

Input [Int queue](/app/src/test/java/com/igorwojda/datastructure/queue/int/IntQueue.md) Change to file relative Result * [Int queue](../int/IntQueue.md)

Input * [Int queue](../int/IntQueue.md) Change to file relative Result [Int queue](/app/src/test/java/com/igorwojda/datastructure/queue/int/IntQueue.md)

[vsch]

@igorwojda, don’t worry about “not getting everything” in markdown limitations right away. Markdown’s apparent simplicity is very misleading. It has a lot of caveats that are not obvious without spending a lot of time in the guts of its implementation.

No need to sensor your ideas on my account. Your suggestions will either let you learn quicker from my answers about what is there or why it cannot be, or I will pick up a great idea for the next “I can’t work without it” feature.

Some features I really did not think of at all so they were a fresh look on how to work with markdown.

Others, were more of a conflict of interest. As developer and a user of the plugin I have a conflict of interest when it comes to adding new features. Yes they will save time for me as a user, but I have to spend a lot of time implementing them as a developer. So there is a natural tendency to avoid adding new features unless I am so fed up with the inefficiency that I can’t take it.

When a user complains about something and I recognize that my only justification is “I don’t want to put in the effort”, I get motivated into seriously looking at the effort or the benefit of the result and usually wind up implementing it.

So far without regrets about any of these since they led to other great features, as is always the case with good ideas.

[igorwojda]

I didn’t mean to add the custom protocol but thanks for the answer as now I have a better understanding of the problem. I guess the names are the only thing here that can be improved.