Giter Club home page Giter Club logo

emacs-conflict's People

Contributors

ibizaman avatar zemja avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

emacs-conflict's Issues

ivy-read: Wrong type argument: symbolp, "Completion conflict history"

The unquoted symbol emacs-conflict--conflict-history in the function emacs-conflict--pick-a-conflict causes errors in Spacemacs when using Helm or Ivy. Quoting the symbol solves the error when using Ivy, but not when using Helm. Removing the symbol fixes functionality for both Ivy and Helm.
As it appears that this symbol does not add functionality, it might be better to just remove it.

Backup or trash conflict file instead of remove

Thank you for this very useful tool!

I have a suggestion regarding the deletion of conflict files.
As it can easily happen that one does a mistake when resolving a conflict and first notices it a bit later, I find it problematic to delete the conflict file right-away. Currently, emacs-conflict-resolve-conflicts asks whether to delete after quitting ediff. If one doesn't delete it, it will of course be presented again for resolving, which one doesn't want either.

My suggestion would be that in addition to delete or not delete there is another option, "archive" or "trash" (or both). It would move the conflict file to the trash or to a configurable directory.
Or it renames myfile.sync-conflict-xxx.org to myfile.sync-conflict-xxx-resolvedYYYYMMDD-HHMMSS.org, which has the advantage that the file can be kept in the same directory without being recognized as a conflict (when adapting the regex accordingly).

With this, after resolving a conflict, the function could ask for (a)rchive, (t)rash, (d)elete, (k)eep.
There should also be a variable where one can set the choice permanently, where I can imagine that "trash" or "archive" would be the preferable choices.

Now if one messed up a resolving and the file is in the archive or the trash, one can simply use ediff manually with it, or in the case of renamed files, there could be a special function that searches for "resolved" conflict files instead of new conflict files.

As a bonus, there would be a cleanup function which deletes (or trashes) archived/resolved conflict files when they become too old or exceed a certain number per file. This function could be called (optionally) after each call to emacs-conflict-resolve-conflicts.

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.