How do I stop ksnapshot from defaulting to filenames that are based on the last-saved file, but -- annoyingly -- with a digit changed? (Every time, I have to manually change the first number that appears in the filename back to what it should be.)
Doc
Anno domini 2026 Tue, 10 Nov 13:23:15 -0700 D. R. Evans via tde-users scripsit:
How do I stop ksnapshot from defaulting to filenames that are based on the last-saved file, but -- annoyingly -- with a digit changed? (Every time, I have to manually change the first number that appears in the filename back to what it should be.)
The brutal way: edit .trinity/share/config/ksnapshotrc - then make it readonly :)
Nik
Doc
Dr. Nikolaus Klepp via tde-users wrote on 11/10/26 1:29 PM:
Anno domini 2026 Tue, 10 Nov 13:23:15 -0700
The brutal way: edit .trinity/share/config/ksnapshotrc - then make it readonly :)
And what magic line do I need to put in that file? The Handbook doesn't say anything about that file at all.
The Handbook does say "If multiple snapshots are taken, the filename is automatically incremented to prevent you from overwriting previous snapshots", but it seems that that happens even if only a single snapshot is taken: the program seems to increment the first number in the last-used filename.
I suppose I can imagine cases in which that might be useful. But to make it the default seems bizarre. Anyway, regardless, it's hugely annoying to me to have to fix it each time I take a screenshot.
Doc
Anno domini 2026 Tue, 10 Nov 15:18:10 -0700 D. R. Evans via tde-users scripsit:
Dr. Nikolaus Klepp via tde-users wrote on 11/10/26 1:29 PM:
Anno domini 2026 Tue, 10 Nov 13:23:15 -0700
The brutal way: edit .trinity/share/config/ksnapshotrc - then make it readonly :)
And what magic line do I need to put in that file? The Handbook doesn't say anything about that file at all.
you set the filename to whatever you want. when ksnapshot is closed and cannot write the file, then the next time it's started you get the filename you put in there. naturally this will not work when you take a series of snapshots whithour closing ksanpshop.
The Handbook does say "If multiple snapshots are taken, the filename is automatically incremented to prevent you from overwriting previous snapshots", but it seems that that happens even if only a single snapshot is taken: the program seems to increment the first number in the last-used filename.
I suppose I can imagine cases in which that might be useful. But to make it the default seems bizarre. Anyway, regardless, it's hugely annoying to me to have to fix it each time I take a screenshot.
Doc
On Tuesday 10 November 2026 21:23:15 D. R. Evans via tde-users wrote:
How do I stop ksnapshot from defaulting to filenames that are based on the last-saved file, but -- annoyingly -- with a digit changed? (Every time, I have to manually change the first number that appears in the filename back to what it should be.)
Doc
I find this quite useful when taking a range of snapshots, actually.
Thierry
Thierry de Coulon via tde-users wrote on 11/10/26 2:05 PM:
I find this quite useful when taking a range of snapshots, actually.
So today I have saved three screenshots: c8k-10m c8k-15m c8k-20m recording the three times that I have contacted the ham radio station C8K in Mozambique today. Imagine how annoying it is that if I contact him again on, say the 40m band, the default from ksnapshot will be c9k-20m.
It's a small thing, I know, but defaulting to this behaviour seems like the programmer thinking (s)he knows better than I do how I want files to be named.
I have no objection at all to this behaviour being available. It just seems bizarre to make it the default.
Doc
On Tuesday 10 November 2026 14:24:46 D. R. Evans via tde-users wrote:
Thierry de Coulon via tde-users wrote on 11/10/26 2:05 PM:
I find this quite useful when taking a range of snapshots, actually.
So today I have saved three screenshots: c8k-10m c8k-15m c8k-20m recording the three times that I have contacted the ham radio station C8K in Mozambique today. Imagine how annoying it is that if I contact him again on, say the 40m band, the default from ksnapshot will be c9k-20m.
It's a small thing, I know, but defaulting to this behaviour seems like the programmer thinking (s)he knows better than I do how I want files to be named.
I have no objection at all to this behaviour being available. It just seems bizarre to make it the default.
Doc
I agree with Doc here. To make this the default setting is totally annoying.
There is some glitch here, however. I did try to change settings like Nik advised, and that doesn't seem to work, either. It may be that one needs to write some special line or command, but that leaves it up to me to guess what that might be.
If Nik knows what to write, or where to insert that magic command, please tell us.
As for this method (editing these -rc config files), this generally works like a charm, with almost any TDE applications that have such files associated with them; for example, tdenetworkmanagerrc, and a few others that I have been editing for years.
Bill
Anno domini 2026 Tue, 10 Nov 14:44:20 -0800 William Morder via tde-users scripsit:
On Tuesday 10 November 2026 14:24:46 D. R. Evans via tde-users wrote:
Thierry de Coulon via tde-users wrote on 11/10/26 2:05 PM:
I find this quite useful when taking a range of snapshots, actually.
So today I have saved three screenshots: c8k-10m c8k-15m c8k-20m recording the three times that I have contacted the ham radio station C8K in Mozambique today. Imagine how annoying it is that if I contact him again on, say the 40m band, the default from ksnapshot will be c9k-20m.
It's a small thing, I know, but defaulting to this behaviour seems like the programmer thinking (s)he knows better than I do how I want files to be named.
I have no objection at all to this behaviour being available. It just seems bizarre to make it the default.
Doc
I agree with Doc here. To make this the default setting is totally annoying.
There is some glitch here, however. I did try to change settings like Nik advised, and that doesn't seem to work, either. It may be that one needs to write some special line or command, but that leaves it up to me to guess what that might be.
If Nik knows what to write, or where to insert that magic command, please tell us.
You can set "filename[$e]=file:///tmp/30.png" in the cinfig file to whatever you want. That name is used as the filename for the next snapshot. Problem is, you need to exit ksnapshot to set the next filename, so this limits your freedom. Anyway, you can create a wrapper like this:
#/bin/bash sed 's#^filename.*$#filename[$e]=file///tmp/'$(date +%Y-%m-%d_%H:%M:%S)'.png#' ~/.trinity/share/config/ksnapshotrc ksnapshot
I don't know how to redirect the "Print" hotkey function to your wrapper in a propper way, but this may work:
In ~/.trinity/share/config/khotkeysrc you find (hoefully) entries like this - strangely I have 2 of these: [Data_4_2Actions0] CommandURL=ksnapshot -c Type=COMMAND_URL
Replace the part right "CommadURL=" with the location of your wrapper (or put your wrapper in your $PATH). Next time "khotkeys" loads is configuration (which is usally when you log in again) then your wrapper should be called when you press the "Print"-key.
Well ... it looks like "khotkeys" is ancient and does crasy stuff. I my case it grabs <ctrl>+<cursor> and I can't find a way to disble that.
Nik
As for this method (editing these -rc config files), this generally works like a charm, with almost any TDE applications that have such files associated with them; for example, tdenetworkmanagerrc, and a few others that I have been editing for years.
Bill
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
Thierry de Coulon composed on 2026-11-10 22:05 (UTC+0100):
D. R. Evans wrote:
How do I stop ksnapshot from defaulting to filenames that are based on the last-saved file, but -- annoyingly -- with a digit changed? (Every time, I have to manually change the first number that appears in the filename back to what it should be.)
I find this quite useful when taking a range of snapshots, actually.
Not me. My snapshots invariably include an unformatted iso8601 date. Tomorrow or the next day or the next should not be assumed.
D. R. Evans via tde-users wrote:
How do I stop ksnapshot from defaulting to filenames that are based on the last-saved file, but -- annoyingly -- with a digit changed? (Every time, I have to manually change the first number that appears in the filename back to what it should be.)
If I were you, I would file a feature request on TGW to include a configuration option (checkbox) to the interface/widget.
In KSnapshot there is a function/method void KSnapshot::autoincFilename() that does increment the (first) number if there is any in the file name. If not it adds one to the end of the filename (as far as I understand the code). By adding a checkbox, lets say "incremental numeration" or "increment numbering", a conditional check could be introduced to the code to call the function or not.
Otherwise you could do "Save As ..." and overwrite a file with the same name. In this case it does not increment any numbers.
BR
deloptes via tde-users wrote on 11/11/26 7:48 AM:
D. R. Evans via tde-users wrote:
How do I stop ksnapshot from defaulting to filenames that are based on the last-saved file, but -- annoyingly -- with a digit changed? (Every time, I have to manually change the first number that appears in the filename back to what it should be.)
If I were you, I would file a feature request on TGW to include a configuration option (checkbox) to the interface/widget.
I plan to do that when I get a moment.
Otherwise you could do "Save As ..." and overwrite a file with the same name. In this case it does not increment any numbers.
I just tested this, and here "Save As..." does present a default name with digits incremented. Which is, I think, exactly what I was doing and brought me here in the first place :-)
Doc
D. R. Evans via tde-users wrote:
I just tested this, and here "Save As..." does present a default name with digits incremented. Which is, I think, exactly what I was doing and brought me here in the first place :-)
... overwrite a file with the same name (to move you forward from here)