subject:"Re\: Seamonkey To Browser"

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-06 Thread User


J. Weaver Jr. wrote on 2017.01.06 6:55:

Using 2.47 (build 20161222015808), the "Components.classes" script listed
below does _nothing_ when run in the error console.  -JW


I was really waiting for someone to say something like that. I noticed that the
original expression did not result in any action in the error console and really
needed someone to point out that some elements in that expression is no longer
valid as of SM 2.46. If we could rework that expression to something that
evaluates to an action for SM 2.46 onwards, that would be useful, even though
the use of the error console to clear browser history by number of days is a bit
beyond the average end user's interest / capability to handle.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-06 Thread David E. Ross

On 1/6/2017 7:47 AM, Frank-Rainer Grahl wrote:
> For what's it worth: removeVisitsByTimeframe war removed in:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1261313
> 
> But if the information is correct this would be for SeaMonkey 2.48.
> 
> FRG

Even before it was implemented, many end-users expressed negative
opinions about removing the capability to expire browser history in
terms of the age of the history entry.  Many of those comments appeared
in the Mozilla Wiki that proposed and explained the change, but all
those comments were deleted (by the author of the Wiki who was the
developer of the change?).

Over 5,000 users downloaded the "Expire history by days" extension,
which will likely be broken by bug #1261313.  This creates an urgency to
implement bug #1246424.  See
.

-- 

David E. Ross
.

The only reason we have so many laws is that not enough people will do
the right thing.  (© 1997 by David Ross)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-06 Thread Frank-Rainer Grahl

For what's it worth: removeVisitsByTimeframe war removed in:

https://bugzilla.mozilla.org/show_bug.cgi?id=1261313

But if the information is correct this would be for SeaMonkey 2.48.

FRG

J. Weaver Jr. wrote:
Using 2.47 (build 20161222015808), the "Components.classes" script listed
below does _nothing_ when run in the error console. -JW

User wrote:

Ant wrote on 2017.01.04 18:46:

On 1/4/2017 5:24 PM, User wrote:

Ant wrote on 2017.01.04 4:43:

On 1/3/2017 9:36 PM, David E. Ross wrote: ...

Try one of the other work-arounds in bug #660646. One suggests a
PrefBar
button; if you have the PrefBar extension installed, the Expire
History
button can be added from
. Although I
created that button, I now use the "Expire history by days" extension
from
.

I
know it works with SeaMonke 2.46; I do not know if the PrefBar button
still
works with 2.46.

...

I second this PrefBar suggestion since I still use its purge my SM's
history
daily to keep only the last 29 days. Its JS button says:

"// This script was suggested by "al_9x" in a comment in bug #660646
Components.classes['@mozilla.org/browser/nav-history-service;1'].getService(Components.interfaces.nsIBrowserHistory).removeVisitsByTimeframe(0,

(new Date().setHours(0, 0, 0, 0) - (parseInt(prompt('Days of
history to
keep', 29)) - 1) * 24 * 60 * 60 * 1000) * 1000 - 1)"

I did read about the PrefBar extension. However, I thought I had
recalled
reading in that Buzilla thread that the PrefBar was using exactly the
same
expression internally do purge browser history. If that is the case,
that would
mean that PrefBar would no longer work with SM 2.46, since that is my
problem in
the first place, that the expression no longer works in the error
console
evaluation. Are you currently using PrefBar in SM 2.46? I have no
verification
from anyone that PrefBar, which uses the exact same expression, is
currently
working in SM 2.46.

It seems to work for my SM since I quick check my histories often.
When I purge
the histories, I can feel the small short pauses too.

I reviewed the entire thread and I have no confirmation of what SM
version you are using PrefBar with for deleting your browser history.
Are you on SM 2.46 or another version? The other user in this thread is
on SM 2.46 but appears not to be using his installed PrefBar for browser
history deletion so I still have no confirmation on whether PrefBar
works in SM 2.46. If it does, then that doesn't make sense because
PrefBar essentially integrated the original expression lifted from that
Bugzilla thread and since that expression no longer works in the SM 2.46
error console, I don't see how the PrefBar using the exact same
expression in SM 2.46 would be functional.

Usually I would go into SQLite Manager extension installed in SM, run
the PLACES.SQLITE compacting, then run the expression in the SM error
console, and run the SQLite Manager compacting one more time and would
notice a major reduction in the PLACES.SQLITE file size, which then
confirms that the expression did its job.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-06 Thread J. Weaver Jr.

Using 2.47 (build 20161222015808), the "Components.classes" script
listed below does _nothing_ when run in the error console. -JW

User wrote:

Ant wrote on 2017.01.04 18:46:

On 1/4/2017 5:24 PM, User wrote:

Ant wrote on 2017.01.04 4:43:

On 1/3/2017 9:36 PM, David E. Ross wrote: ...

I
know it works with SeaMonke 2.46; I do not know if the PrefBar button
still
works with 2.46.

...

I second this PrefBar suggestion since I still use its purge my SM's
history
daily to keep only the last 29 days. Its JS button says:

(new Date().setHours(0, 0, 0, 0) - (parseInt(prompt('Days of
history to
keep', 29)) - 1) * 24 * 60 * 60 * 1000) * 1000 - 1)"

It seems to work for my SM since I quick check my histories often.
When I purge
the histories, I can feel the small short pauses too.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-06 Thread User

Ant wrote on 2017.01.04 18:46:

On 1/4/2017 5:24 PM, User wrote:

Ant wrote on 2017.01.04 4:43:

On 1/3/2017 9:36 PM, David E. Ross wrote: ...

Try one of the other work-arounds in bug #660646. One suggests a
PrefBar
button; if you have the PrefBar extension installed, the Expire History
button can be added from
. Although I
created that button, I now use the "Expire history by days" extension
from
.
I
know it works with SeaMonke 2.46; I do not know if the PrefBar button
still
works with 2.46.

...

I second this PrefBar suggestion since I still use its purge my SM's
history
daily to keep only the last 29 days. Its JS button says:

(new Date().setHours(0, 0, 0, 0) - (parseInt(prompt('Days of history to
keep', 29)) - 1) * 24 * 60 * 60 * 1000) * 1000 - 1)"

I did read about the PrefBar extension. However, I thought I had recalled
reading in that Buzilla thread that the PrefBar was using exactly the same
expression internally do purge browser history. If that is the case,
that would
mean that PrefBar would no longer work with SM 2.46, since that is my
problem in
the first place, that the expression no longer works in the error console
evaluation. Are you currently using PrefBar in SM 2.46? I have no
verification
from anyone that PrefBar, which uses the exact same expression, is
currently
working in SM 2.46.

It seems to work for my SM since I quick check my histories often. When I purge
the histories, I can feel the small short pauses too.

I reviewed the entire thread and I have no confirmation of what SM version you
are using PrefBar with for deleting your browser history. Are you on SM 2.46 or
another version? The other user in this thread is on SM 2.46 but appears not to
be using his installed PrefBar for browser history deletion so I still have no
confirmation on whether PrefBar works in SM 2.46. If it does, then that doesn't
make sense because PrefBar essentially integrated the original expression lifted
from that Bugzilla thread and since that expression no longer works in the SM
2.46 error console, I don't see how the PrefBar using the exact same expression
in SM 2.46 would be functional.

Usually I would go into SQLite Manager extension installed in SM, run the
PLACES.SQLITE compacting, then run the expression in the SM error console, and
run the SQLite Manager compacting one more time and would notice a major
reduction in the PLACES.SQLITE file size, which then confirms that the
expression did its job.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-04 Thread David E. Ross

On 1/4/2017 5:24 PM, User wrote:
> Ant wrote on 2017.01.04 4:43:
>> On 1/3/2017 9:36 PM, David E. Ross wrote: ...
>>> Try one of the other work-arounds in bug #660646.  One suggests a PrefBar
>>> button; if you have the PrefBar extension installed, the Expire History
>>> button can be added from
>>> .  Although I
>>> created that button, I now use the "Expire history by days" extension from
>>> . I
>>> know it works with SeaMonke 2.46; I do not know if the PrefBar button still
>>> works with 2.46.
>> ...
>>
>> I second this PrefBar suggestion since I still use its purge my SM's history
>> daily to keep only the last 29 days. Its JS button says:
>>
>> "//  This script was suggested by "al_9x" in a comment in bug #660646
>> Components.classes['@mozilla.org/browser/nav-history-service;1'].getService(Components.interfaces.nsIBrowserHistory).removeVisitsByTimeframe(0,
>>
>>  (new Date().setHours(0, 0, 0, 0) - (parseInt(prompt('Days of history to
>> keep', 29)) - 1) * 24 * 60 * 60 * 1000) * 1000 - 1)"
> 
> I did read about the PrefBar extension. However, I thought I had recalled
> reading in that Buzilla thread that the PrefBar was using exactly the same
> expression internally do purge browser history. If that is the case, that 
> would
> mean that PrefBar would no longer work with SM 2.46, since that is my problem 
> in
> the first place, that the expression no longer works in the error console
> evaluation. Are you currently using PrefBar in SM 2.46? I have no verification
> from anyone that PrefBar, which uses the exact same expression, is currently
> working in SM 2.46.
> 

I am using PrefBar 7.1.0 with SeaMonkey 2.46.  HOWEVER, that is for
other PrefBar capabilities.

As I indicated earlier, I switched to using the "Expire history by days"
extension.  It is version 1.2.0 converted at
 for compatibility with
SeaMonkey.  The extension's current version 1.2.1 cannot be converted
successfully.

-- 

David E. Ross
.

The only reason we have so many laws is that not enough people will do
the right thing.  (© 1997 by David Ross)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-04 Thread Ant

On 1/4/2017 5:24 PM, User wrote:

Ant wrote on 2017.01.04 4:43:

On 1/3/2017 9:36 PM, David E. Ross wrote: ...

Try one of the other work-arounds in bug #660646. One suggests a
PrefBar
button; if you have the PrefBar extension installed, the Expire History
button can be added from
. Although I
created that button, I now use the "Expire history by days" extension
from
.
I
know it works with SeaMonke 2.46; I do not know if the PrefBar button
still
works with 2.46.

...

I second this PrefBar suggestion since I still use its purge my SM's
history
daily to keep only the last 29 days. Its JS button says:

(new Date().setHours(0, 0, 0, 0) - (parseInt(prompt('Days of history to
keep', 29)) - 1) * 24 * 60 * 60 * 1000) * 1000 - 1)"

I did read about the PrefBar extension. However, I thought I had recalled
reading in that Buzilla thread that the PrefBar was using exactly the same
expression internally do purge browser history. If that is the case,
that would
mean that PrefBar would no longer work with SM 2.46, since that is my
problem in
the first place, that the expression no longer works in the error console
evaluation. Are you currently using PrefBar in SM 2.46? I have no
verification
from anyone that PrefBar, which uses the exact same expression, is
currently
working in SM 2.46.

It seems to work for my SM since I quick check my histories often. When
I purge the histories, I can feel the small short pauses too.

--
"Applied mathematics will always need pure mathematics, just as
anteaters will always need ants." --Paul Halmos
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.

/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-04 Thread User

Ant wrote on 2017.01.04 4:43:

On 1/3/2017 9:36 PM, David E. Ross wrote: ...

Try one of the other work-arounds in bug #660646. One suggests a PrefBar
button; if you have the PrefBar extension installed, the Expire History
button can be added from
. Although I
created that button, I now use the "Expire history by days" extension from
. I
know it works with SeaMonke 2.46; I do not know if the PrefBar button still
works with 2.46.

...

I second this PrefBar suggestion since I still use its purge my SM's history
daily to keep only the last 29 days. Its JS button says:

(new Date().setHours(0, 0, 0, 0) - (parseInt(prompt('Days of history to
keep', 29)) - 1) * 24 * 60 * 60 * 1000) * 1000 - 1)"

I did read about the PrefBar extension. However, I thought I had recalled
reading in that Buzilla thread that the PrefBar was using exactly the same
expression internally do purge browser history. If that is the case, that would
mean that PrefBar would no longer work with SM 2.46, since that is my problem in
the first place, that the expression no longer works in the error console
evaluation. Are you currently using PrefBar in SM 2.46? I have no verification
from anyone that PrefBar, which uses the exact same expression, is currently
working in SM 2.46.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-04 Thread David E. Ross

On 1/4/2017 4:43 AM, Ant wrote:
> On 1/3/2017 9:36 PM, David E. Ross wrote:
> ...
>> Try one of the other work-arounds in bug #660646.  One suggests a
>> PrefBar button; if you have the PrefBar extension installed, the Expire
>> History button can be added from
>> .  Although I
>> created that button, I now use the "Expire history by days" extension
>> from
>> .
>>  I know it works with SeaMonke 2.46; I do not know if the PrefBar button
>> still works with 2.46.
> ...
> 
> I second this PrefBar suggestion since I still use its purge my SM's 
> history daily to keep only the last 29 days. 

[snipped]

I use the "Expire history by days" extension because it works
automatically and does not require my manual selection of a PrefBar
button.  "Expire history by days" has an option -- reached through its
entry in the Ad-ons Manager -- to set the number of days of history
retention.

-- 
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-04 Thread Ant


On 1/3/2017 9:36 PM, David E. Ross wrote:
...

Try one of the other work-arounds in bug #660646.  One suggests a
PrefBar button; if you have the PrefBar extension installed, the Expire
History button can be added from
.  Although I
created that button, I now use the "Expire history by days" extension
from
.
 I know it works with SeaMonke 2.46; I do not know if the PrefBar button
still works with 2.46.

...

I second this PrefBar suggestion since I still use its purge my SM's 
history daily to keep only the last 29 days. Its JS button says:


"//  This script was suggested by "al_9x" in a comment in bug #660646
Components.classes['@mozilla.org/browser/nav-history-service;1'].getService(Components.interfaces.nsIBrowserHistory).removeVisitsByTimeframe(0, 


 (new Date().setHours(0, 0, 0, 0)
  - (parseInt(prompt('Days of history to keep', 29)) - 1)
  * 24 * 60 * 60 * 1000) * 1000 - 1)"
--
"I ate ants. They weren't that bad." --Leslie Hope
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( )   Axe ANT from its address if e-mailing privately.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.46 browser history manual deletion expression

2017-01-03 Thread David E. Ross

On 1/3/2017 5:32 PM, User wrote:
> Prior to upgrading to SM 2.46, I have used the following manual workaround 
> shown
> on comment 7 at this Bugzilla bug record below to delete browser history but
> preserve the most recent 30 days:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=660646#c7
> 
> Using this expression:
> 
> Components.classes['@mozilla.org/browser/nav-history-service;1'].getService(Components.interfaces.nsIBrowserHistory).removeVisitsByTimeframe(0,
> (new Date().setHours(0, 0, 0, 0) - (parseInt(prompt('Days of history to keep',
> 30)) - 1) * 24 * 60 * 60 * 1000) * 1000 - 1)
> 
> I just recently upgraded to SM 2.46 and found that using the expression I
> mentioned above used in the SM error console's evaluation field to delete
> browser history except the last 30 days, no longer works. The NUMBER OF DAYS
> prompt that is supposed to appear with this expression no longer appears when
> the expression is evaluated in the error console. I'm not sure if this problem
> now have anything to do with the mentioned changes regarding the Javascript
> debugger interface at this URL:
> 
> http://www.seamonkey-project.org/releases/seamonkey2.46/
> 
> and if so, what if any, is the workaround solution to execute the same
> expression elsewhere in SM 2.46? This method has worked well for me up until 
> now
> and I'm guessing that the expression above just needs some update as some of 
> the
> elements the expression is referring to may now be invalid in SM 2.46. Thanks
> for any advise from advance users / coders.
> 

Try one of the other work-arounds in bug #660646.  One suggests a
PrefBar button; if you have the PrefBar extension installed, the Expire
History button can be added from
.  Although I
created that button, I now use the "Expire history by days" extension
from
.
 I know it works with SeaMonke 2.46; I do not know if the PrefBar button
still works with 2.46.

"Expire history by days" 1.2.1 cannot be used by SeaMonkey.  It is
necessary to get the older version 1.2.0 after it has been converted via
.  If you send me an E-mail
message, I will reply with a copy of the converted 1.2.0 .xpi file.  My
real E-mail address is in the Organization header field of this
newsgroup reply; look at the message source to find the Organization
header field.

-- 
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

33 matches

Mail list logo