Re: [arch-general] OK so HARDWARECLOCK="localtime" is "strongly discouraged" BUT???
On Jul 12, 2011 8:19 AM, "Joe(theWordy)Philbrook" wrote: Dude ... just set UTC and forget about it ... forever :-) The wisdom of others frees time to build more wisdom of self. C Anthony
Re: [arch-general] Content of new text file
On Wed, 13 Jul 2011, Squall Lionheart wrote: > > > When using Dolphin in KDE4 to *Create New > Text File...* the new > > > file is not empty, it contains a space and a newline character. I > > > have looked for some kind of setting or template file that controls > > > this default and have not been successful. I was wondering if anyone > > > knows how to modify this behavior or can provide a link to a how to. > > > My goal here is to simply create an empty file just like if you used > > > *touch newfile.txt*. > > > > Looks like a case for https://bugs.kde.org. > > If it comes down to it being a bug, I'll file a report. Just want to make > sure it's not just a template somewhere first. /usr/share/templates/TextFile.desktop will let you configure it. You can point the URL variable to your desired template file. Pete.
Re: [arch-general] Content of new text file
On Wed, Jul 13, 2011 at 3:37 PM, Heiko Baums wrote: > Am Wed, 13 Jul 2011 15:00:37 -0600 > schrieb Squall Lionheart : > > > When using Dolphin in KDE4 to *Create New > Text File...* the new > > file is not empty, it contains a space and a newline character. I > > have looked for some kind of setting or template file that controls > > this default and have not been successful. I was wondering if anyone > > knows how to modify this behavior or can provide a link to a how to. > > My goal here is to simply create an empty file just like if you used > > *touch newfile.txt*. > > Looks like a case for https://bugs.kde.org. > > Heiko > If it comes down to it being a bug, I'll file a report. Just want to make sure it's not just a template somewhere first.
Re: [arch-general] Content of new text file
Am Wed, 13 Jul 2011 15:00:37 -0600 schrieb Squall Lionheart : > When using Dolphin in KDE4 to *Create New > Text File...* the new > file is not empty, it contains a space and a newline character. I > have looked for some kind of setting or template file that controls > this default and have not been successful. I was wondering if anyone > knows how to modify this behavior or can provide a link to a how to. > My goal here is to simply create an empty file just like if you used > *touch newfile.txt*. Looks like a case for https://bugs.kde.org. Heiko
Re: [arch-general] Content of new text file
On 07/13/2011 05:00 PM, Squall Lionheart wrote: Hello, When using Dolphin in KDE4 to *Create New> Text File...* the new file is not empty, it contains a space and a newline character. I have looked for some kind of setting or template file that controls this default and have not been successful. I was wondering if anyone knows how to modify this behavior or can provide a link to a how to. My goal here is to simply create an empty file just like if you used *touch newfile.txt*. Thank you Nope. But if you hear how to solve that, please post back. That's been a peeve of mine with KDE for years now. (Konqueror suffers from the same problem.) DR
[arch-general] Content of new text file
Hello, When using Dolphin in KDE4 to *Create New > Text File...* the new file is not empty, it contains a space and a newline character. I have looked for some kind of setting or template file that controls this default and have not been successful. I was wondering if anyone knows how to modify this behavior or can provide a link to a how to. My goal here is to simply create an empty file just like if you used *touch newfile.txt*. Thank you -- Yesterday is history. Tomorrow is a mystery. Today is a gift. That's why its called the present. Headmaster Squall :: The Wired/Section-9 Close the world txen eht nepo $3R14L 3XP3R1M3NT$ #L41N http://twitter.com/headmastersqual
Re: [arch-general] [arch-dev-public] dropping tcp_wrapper support
> > > I would say the same, but a todo list isn't a to-done list, so keep > that in mind. He also pointed out that I got little to no feedback > when I asked about this both a year and six months ago, so > expectations are pretty low this time around. I'm sure if there were > serious objections people would raise them and we could address them. > > This is worthy of a news article once we move packages to core only > because it could expose some services people didn't previously expect > to need to protect. > > -Dan > As far as feedback goes, I have used tcp-wrappers a great deal in the past, but not for many years. And the fact that it needs to be so heavily patched suggests that we should not be using it anyway. I agree that we should not have to maintain it anymore, it is an outdated security system that usually gets in the way, and Arch is the only distro I use that turns it on by default. +1
