-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Add support of syncing just a single file #1116
Comments
That's more like the use-case for "synctool".
https://github.com/walterdejong/synctool
…On Sat, 01 Feb 2025 08:34:23 -0800 "Drugoy" ***@***.***> wrote:
I'd like to keep some config files synced between the machines.
I don't want to bother with creating an extra dir for those files and
symlink them for the actual paths of those configs. I want to be able
to do a file-to-file sync.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this
thread.Message ID: ***@***.***>
--
Drexel University |/ / · ν · Chuck Lane |D
======]--->---C-----π+--< Disque 911 |U
Particle Physics \ \ ~~ e+~~ 215-895-1545 |N
***@***.*** -μ+--+νν |E
|
@celane thanks for suggesting another tool, but I honestly would prefer much such functionality added to Unison. |
Please bring this up on the users list. It's not clear to me that it's impossible to configure what you want. (Help is inappropriate in issues, which is why I am pointing you to the users list.) |
@gdt I believe it's fine to discuss the issue here, because there seems to be one and it needs some changes made in different places. If we simplify the task a little bit to make it sync file And ONLY if you simplify the task even more to make it sync file That's like not the same task, I believe the current functionality is not enough to solve a more general task of being able to use Unison to sync one file with another, regardless of their location (which may or may not be two different locations) and names (which may or may not match). |
The point of directing you to the lists is that there are very few that follow the repository, and many on the lists. The project does not accept the dictates of github culture. I've add this feature request to the list of things that are unlikely to be implemented: https://github.com/bcpierce00/unison/wiki/Feature-Requests and therefore closed it. if you intend to implement this (code, doc changes, tests), please feel free to bring it up on unison-hackers@. I have a strong bias that unison is already too complicated, so it will need either an elegant approach or a good argument that the additional complexity is a good tradeoff relative to the overall benefit to the user-using community. |
I think this is worth reopening. If not completely fix it, there is at least a low-effort option to improve the situation. This is a GUI issue (seems to be a limitation in the GTK file chooser). Syncing single files (with differing names) is well supported on the command line or when you craft the profile manually. It would be no problem adding a clarifying message in the affected GUI dialogs. |
My issue here is that the 'using the tracker' document defines that the tracker, for feature requests is only for fully baked requests. This was not one, and I asked the reporter to engage on the list, which has a broader audience, vs the issue tracker, which comes down to being responded to by a very small number of people,, and they declined to do so. I did suspect this could be handled in the TUI (but the issue tracker is not a help forum and i decilne to go there on principle). With the message added, this seems adequately addressed. Followup from @Drugoy or anyone else welcome on the lists. |
What does engaging with broader audience have to do with your claim of this feature request not being a 'fully baked' one? p.s.: I am not entirely sure (as I don't speak OCaml), but it looks like your pull request #1117 is incorrect. |
That's the assistant, the opposite of manual :) |
@Drugoy Please test the CI builds from the PR and comment (in the PR is probably best). |
I'd like to keep some config files synced between the machines.
I don't want to bother with creating an extra dir for those files and symlink them for the actual paths of those configs.
I want to be able to do a file-to-file sync.
The text was updated successfully, but these errors were encountered: