Giter VIP home page Giter VIP logo

Comments (4)

kevinmatthes avatar kevinmatthes commented on May 31, 2024 1

@AmmarAbouZor

Thanks for pointing out the access to the global configuration! I did only know about the local one, by now.

One thing that might be considerable is the ability to configure the preferred Git editor per repository. This is especially useful for users who contribute to multiple text editors. These users may have set their favourite editor in the global settings and altered their preferred editor per repository by configuring the respective editor the corresponding project is about. This use case should rather not be underestimated as there are plenty of text editors, especially in the Rust ecosystem where implementing them is very easy; furthermore, I experienced myself that contributors to text editors usually participate in the development of multiple editors (or at least switch to another project when one should become discontinued whilst still the setting regarding the Git editor for the discontinued project is reasonable as the maintainer might decide to work on their project, again).

However, this is a rather exotic edge case as most users cannot be expected to contribute to more than one editor, if any. So, it is up to you how you decide to take this scenario into account for the further development since the current implementation should fit for about 95% of the use cases, I guess.

from tui-journal.

AmmarAbouZor avatar AmmarAbouZor commented on May 31, 2024 1

For that scenario I think the best solution is to configure the editor from tui-journal configurations directly which gives the benefit of having the same experience using the app globally 👍

from tui-journal.

AmmarAbouZor avatar AmmarAbouZor commented on May 31, 2024

This could be useful for cross platform compatibility, since the current implementation has only UNIX in mind. I'll try to implement this and see how it would work

from tui-journal.

AmmarAbouZor avatar AmmarAbouZor commented on May 31, 2024

@kevinmatthes I've found the method git2::Config::open_default() which opens the git global the configurations.

I think it's more useful this way since the users most likely set the editor globally and this way we are not tied to the current directory.
If you think that there are other benefits from using the current directory please let me know

from tui-journal.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.