Skip to content

clipboard-history@axaul: Add a little Clipboard History applet #7196

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

GALLIC-A
Copy link

@GALLIC-A GALLIC-A commented May 8, 2025

This PR adds a new applet: Clipboard History (clipboard-history@axaul)

The applet allows users to:

  • View and reuse recent clipboard entries
  • Configure clipboard check interval and history size
  • Define a keyboard shortcut for fast access
  • Enable debug logging for development/testing (or just to check that everything is ok)

This is the initial submission.
The applet was originally developed by me, on my personal GitHub repository:
https://github.com/GALLIC-A/HistoriquePressePapiersPourCinnamon

The commits aren't directly associated with my GitHub account because I'm not logged in under the same name on my operating system. However, I'm the one who developed and submitted this PR.

This applet provides a simple clipboard history manager for the Cinnamon desktop. It allows users to browse, reuse and manage recently copied text entries.

Features include:
- Menu-based access to clipboard history
- Optional debug mode for developers
- Configurable item limit and check interval
- Keyboard shortcut support

The applet does not depend on external package to work.
@GALLIC-A GALLIC-A changed the title Add clipboard-history@axaul : Clipboard History applet clipboard-history@axaul: Add a little Clipboard History applet May 14, 2025
@GALLIC-A
Copy link
Author

Hello, just a friendly reminder - this PR has been open for 3 weeks now.

Please let me know if anything needs to be adjusted or improved for it to be reviewed or merged.
I'd be happy to make any changes if needed.

Thanks for your work.

@@ -0,0 +1 @@
{"author":"Axel GALLIC"}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be your GitHub username.

@rcalixte
Copy link
Member

In general, this seems like it was generated by a large language model. In particular, the translations. That has been attempted before and it did not go over well. There are fantastic and active human translators that contribute so it would be best to leave it to them. It's great that you thought of that and want to see it supported but bad auto-generated translations are worse for everyone.

@fredcw
Copy link
Contributor

fredcw commented May 26, 2025

@rcalixte I'm not questioning your decisions here but I just want to make my position clear regarding AI. I have no problem with the use of AI as such, it's a very useful tool for many things. My issue before was not the use of AI, but rather that it was unedited AI text that, importantly, was intended to be presented as if written by a human when, in fact, no human had any part in it, not a single word, it was zero effort and wasn't even checked for correctness. I think AI generated text is fine if it's edited by a human so that it's what the human intended to say. Also, I see no problem with AI generated code and translations because these are not presented as human communication and do not purport to be written by a human and as long as they're correct then I see no problem. If it works then it works, right?

Anyway, that's my 2 cents, other opinions may vary.

btw, machine translations are actually very good and I used them before in my own applets. Even if they not all 100% correct, they're still a lot better than nothing.

@GALLIC-A GALLIC-A requested a review from rcalixte May 27, 2025 11:55
@GALLIC-A
Copy link
Author

Hello, thank you very much for your reply.
Wanted to answer that once the proper changes made, but I clicked on the wrong button which sent you a review request, I apologize!
I did use an LLM for translations, except for French (which is my native language) and English, I didn’t really realize it was a bad idea.
I agree that it is better to leave the translations to excellent contributors who know what they are doing.
So as soon as I have time to do it, I will delete all the automatically generated translations and keep only the French and English translations that were not generated by an LLM.
I will also correct the file info.json.
Thank you again for your constructive feedback.

@fredcw
Copy link
Contributor

fredcw commented May 27, 2025

I just tested gemini with the following prompt:

Here is the .po file for Spanish (es.po) for a cinnamon applet. Can you fill in the missing Spanish translations:

<es.po file with no translated strings>

Here's @haggen88's translation for trilium-api@beatlink applet:

es.po.txt

and here's gemini's response to the prompt:

es.po.gemini.txt

When I compare these two files, it seems to me with my limited understanding of spanish, that Gemini's version is perfectly fine. There are some minor differences in word choice or phrasing, but none of it appears to be wrong or misleading. Gemini is better than Google translate for this because it understands the context - i.e. terms related to a computer GUI.

@GALLIC-A GALLIC-A changed the title clipboard-history@axaul: Add a little Clipboard History applet clipboard-history@GALLIC-A: Add a little Clipboard History applet Jul 2, 2025
@GALLIC-A GALLIC-A changed the title clipboard-history@GALLIC-A: Add a little Clipboard History applet clipboard-history@axaul: Add a little Clipboard History applet Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants