Re: No firefox on OpenBSD 7.0 i386?
On Fri, 21 Jan 2022, Stuart Longland wrote: On Fri, 21 Jan 2022 07:26:54 +0100 Caspar Schutijser wrote: I find that, even with Firefox configured to separate the two, I'll start keying in an address like `http://some.internal.site/` and Firefox "thinks" I want to do a Google search for `http://`. How did you configure this? I've set keyword.enabled to false in about:config which makes sure it never uses the information in the location bar as a search query. See https://kb.mozillazine.org/Keyword.enabled Hamburger menu → Settings Choose "Search" from the left-hand category list. Click "Add search bar in toolbar" radio button, it should change instantly. It is new to me that having separate widgets is now only a choice. But even as it was the standard to have a separate box for search, firefox did search from the URL box. To disable it was a big "about:config" theatre I cannot reproduce. The old "prefs.js" configuration still works. I know people that do not know the difference between entering an URL and searching in google. To go to their internet banking, they search in google for their bank. Web sites are done for these perhaps average people and for these browsers we are compelled to use. Rod.
Re: No firefox on OpenBSD 7.0 i386?
On Thu, Jan 20, 2022 at 03:18:36PM +1000, Stuart Longland wrote: > On Fri, 7 Jan 2022 15:38:11 + (UTC) > Roderick wrote: > > > With chrome I have a problem, because it does not separate URL > > entry from search entry. > > I find that, even with Firefox configured to separate the two, I'll > start keying in an address like `http://some.internal.site/` and > Firefox "thinks" I want to do a Google search for `http://`. How did you configure this? I've set keyword.enabled to false in about:config which makes sure it never uses the information in the location bar as a search query. See https://kb.mozillazine.org/Keyword.enabled Caspar
Re: Keyboard input problems after disk corruption in crashes. Both in console and xterm.
On January 20, 2022 4:10:28 PM PST, Stuart Henderson
wrote:
>On 2022-01-20, lumidify wrote:
>> On Thu, Jan 20, 2022 at 10:45:27AM -0800, Chris Bennett wrote:
>>> I had several accidental crashes which left lost+found in home folder.
>>> up arrow fails in terminals and left arrow erases to the left instead of
>>> moving.
>>
>> Exactly this behavior happens in vi mode ('set -o vi' in ~/.profile
>> or ~/.kshrc),
>
>or by setting EDITOR=vi thanks to an annoying ksh feature.
>
>> but that seems somewhat unrealistic since I have no idea
>> how it could be caused by the crashes.
>
>some config file could have been corrupted.
>
>
OMG! I was fiddling with some dotfiles suggested in a git repository for a
bunch of things. Some were really good.
I left exactly that by accident when I was experimenting.
Thanks! Saved from disaster.
Chris
Re: No firefox on OpenBSD 7.0 i386?
On 2022-01-20, Riccardo Mottola wrote: > Hi, > > Crystal Kolipe wrote: >> On Fri, Jan 07, 2022 at 03:38:11PM +, Roderick wrote: >>> I just updated OpenBSD to 7.0. After pkg_add -u, it seems >>> firefox was not updated: >> Firefox no longer builds on i386, since shortly after the release of OpenBSD >> 6.9. > > I noticed that to, it is sad. Wonder why? Last time I tried, memory use when compiling Firefox's parts written in Rust was too high. Chromium does build these days though (and may even run, if you're lucky).
Re: Keyboard input problems after disk corruption in crashes. Both in console and xterm.
On 2022-01-20, lumidify wrote:
> On Thu, Jan 20, 2022 at 10:45:27AM -0800, Chris Bennett wrote:
>> I had several accidental crashes which left lost+found in home folder.
>> up arrow fails in terminals and left arrow erases to the left instead of
>> moving.
>
> Exactly this behavior happens in vi mode ('set -o vi' in ~/.profile
> or ~/.kshrc),
or by setting EDITOR=vi thanks to an annoying ksh feature.
> but that seems somewhat unrealistic since I have no idea
> how it could be caused by the crashes.
some config file could have been corrupted.
Keyboard input problems after disk corruption in crashes. Both in console and xterm.
I had several accidental crashes which left lost+found in home folder. up arrow fails in terminals and left arrow erases to the left instead of moving. I have an older version of the home folder that does not have the problem. Since it is both inside and outside of X, what files should I consider? I am using 6.6 amd64 and FVWM2 from ports. I can't update past 6.6. Any help really appreciated! -- Thanks, Chris Bennett
Re: No firefox on OpenBSD 7.0 i386?
On Thu, Jan 20, 2022 at 04:28:45PM +0100, Jan Stary wrote: > > On Fri, 7 Jan 2022 15:38:11 + (UTC) > > Roderick wrote: > > > > > With chrome I have a problem, because it does not separate URL > > > entry from search entry. > > Why is that a problem? Presumably because if you make a typo when entering an URL, it sends the URL string, (which may contain references to a private server), to a search engine.
Re: No firefox on OpenBSD 7.0 i386?
> On Fri, 7 Jan 2022 15:38:11 + (UTC) > Roderick wrote: > > > With chrome I have a problem, because it does not separate URL > > entry from search entry. Why is that a problem?
