webmode settings in source code not honored #151

New Issue

tidux · 2020-05-18T23:14:06Z

tidux commented

2020-05-18 23:14:06 +00:00

I've tried setting "webmode": "lynx", and "webmode": "w3m" in defaults.go but neither setting is used in the resulting binaries. I still get a "Current 'webmode' setting does not allow http/https" error despite both lynx and w3m existing in /usr/bin/. Test system is Debian 10, with Go 1.14.3. There is no INI file.

I've tried setting `"webmode": "lynx",` and `"webmode": "w3m"` in defaults.go but neither setting is used in the resulting binaries. I still get a "Current 'webmode' setting does not allow http/https" error despite both lynx and w3m existing in /usr/bin/. Test system is Debian 10, with Go 1.14.3. There is no INI file.

sloum commented

2020-05-18 23:45:40 +00:00

@tidux

That is very strange that it is not compilling correctly for you. A few questions:

Are you building off of master or develop?
When you launch bombadillo what is the response when you enter the following:
- :check webmode
Seems silly to ask, but always good to sanity check: are you sure you have saved defaults.go with the updated value before compiling?
After lanching Bombadillo does the following command update the value and then work for viewing web links:
- :set webmode lynx

I just pulled master and changed the "webmode" in defaults.go to "lynx" and had no issues (compiled with 1.14.2 on Arch).

Let me know the above when you get a chance. I use a Debian based system as my main system and the Arch system I just used as a secondary and have not run into this issue so I do not think it is a platform issue.

Oh! One more question:

After you compile and run Bombadillo, has a .bombadillo.ini file been created?

@tidux That is very strange that it is not compilling correctly for you. A few questions: - Are you building off of `master` or `develop`? - When you launch bombadillo what is the response when you enter the following: - `:check webmode` - Seems silly to ask, but always good to sanity check: are you sure you have saved `defaults.go` with the updated value _before_ compiling? - After lanching Bombadillo does the following command update the value and then work for viewing web links: - `:set webmode lynx` I just pulled `master` and changed the `"webmode"` in `defaults.go` to `"lynx"` and had no issues (compiled with `1.14.2` on Arch). Let me know the above when you get a chance. I use a Debian based system as my main system and the Arch system I just used as a secondary and have not run into this issue so I do not think it is a platform issue. Oh! One more question: - After you compile and run Bombadillo, has a `.bombadillo.ini` file been created?

sloum added the

bug

label 2020-05-18 23:46:22 +00:00

asdf commented

2020-05-19 03:04:56 +00:00

Just a quick note: it sticks out that the report states there is no INI file.

Changes to defaults.go, followed by a recompile, will not have an impact on settings for a user who already has an ini file (with the exception of the configlocation setting that changes where the ini file is stored).

Could it be that there is an existing configuration file with a different webmode setting in an unexpected location? The actual location can be checked in Bombadillo using the command :check configlocation.

By the way thanks @tidux for the report!

Just a quick note: it sticks out that the report states there is no INI file. Changes to defaults.go, followed by a recompile, will not have an impact on settings for a user who already has an ini file (with the exception of the `configlocation` setting that changes where the ini file is stored). Could it be that there is an existing configuration file with a different webmode setting in an unexpected location? The actual location can be checked in Bombadillo using the command `:check configlocation`. By the way thanks @tidux for the report!

sloum commented

2020-05-19 03:16:38 +00:00

You are very right @asdf . Good thinking! That may be a simple fix here. Hopefully checking the config location that is being used by the binary and then deleting a config if it exists will do the job.

If there is no config at that location, that would definitely be a weird issue. I look forward to hearing back about this one!

You are very right @asdf . Good thinking! That may be a simple fix here. Hopefully checking the config location that is being used by the binary and then deleting a config if it exists will do the job. If there is no config at that location, that would definitely be a weird issue. I look forward to hearing back about this one!

sloum added the

needs-info

label 2020-05-22 16:25:45 +00:00

sloum added the

blocked

label 2020-05-25 05:00:27 +00:00

sloum commented

2020-06-15 06:28:31 +00:00

I am closing this as a stale issue with not enough info to replicate. @tidux feel free to resubmit if you end up with more info.

sloum closed this issue

2020-06-15 06:28:36 +00:00

Sign in to join this conversation.