Tim Smith wrote to GitLab note in main/sbbs <=-
https://gitlab.synchro.net/main/sbbs/-/issues/755#note_5334
I believe my last pull was 4 days ago, it was after your merges,
I havent really seen much action since then, I just now realized
the issue today when a visiting sysop told me of the issue. but
it really does appear it has something to do with the fullscreen
editor not being set right before newuser feedback though. I will
try to tell you what I changed to see if you can make any sense
out of it, but really all I did was add Dueces editor as an
option again, and left both Slyedit options also. before I had
only had slyedit as an option.
and also under slyedit setup I changed:
Native executable stript, Use Shell or context, and record
terminal width all to YES
I believe they were all set to no
I think I may have changed support UTF-8 encoding to YES from NO
also, I cannot remember for sure. I may go look through my old
config files to see. if needed.. I wish I could help more, but I
closed it because I thought it may Had just been something I was
doing wrong.
kk4qbn wrote to Gamgee <=-
Re: Re: SlyEdit.js issue with new user feedback since last
update
By: Gamgee to Tim Smith on Sun May 12 2024 07:53:00
Shell or context, and record terminal width all to YES
I believe they were all set to no
Why would you do that?
because it was the settings for Dueces fullscreen editor, I
copied them, and it worked.
thought it may Had just been something I was doing wrong.
Well...., it was.
Ok, I know this.. but it still was an issue with SlyEdit that
needed to be looked at that could have been a problem sometime
down the road.
On the other hand, gitlab, or the Developer of SlyEdit cannot
really help with the issues you have, so maybe you need to find a different venue to vent your frustrations..
I try to help with any issue people report with SlyEdit or any of my mods. Yesterday, by the time I was able to have a look at it, the issue was already closed, with you saying you changed some settings in your SlyEdit configuration and it worked. I'm not entirely clear on how those settings fixed the issue you reported though. The error you shared in the issue suggested that there may be a point when a new uesr's configured external editor might still be undefined, even after they had chosen SlyEdit. I
kk4qbn wrote to Gamgee <=-
Re: Re: SlyEdit.js issue with new user feedback since last update
By: Gamgee to Tim Smith on Sun May 12 2024 07:53:00
Shell or context, and record terminal width all to YES I believe they
were all set to no
Why would you do that?
because it was the settings for Dueces fullscreen editor, I copied them,
and it worked.
Nope. Just checked all three of those editors (fseditor and two flavors of Slyedit) in my settings, and all those parameters are set to "NO". Like they are on all SBBS systems. They are all .js programs so there would be no reason to set those settings to YES. <SHRUG>
thought it may Had just been something I was doing wrong.
Well...., it was.
Ok, I know this.. but it still was an issue with SlyEdit that needed to
be looked at that could have been a problem sometime down the road.
On the other hand, gitlab, or the Developer of SlyEdit cannot really help
with the issues you have, so maybe you need to find a different venue to
vent your frustrations..
Huh? Vent my frustrations? Not following you here. I don't have any frustrations, and my editors all work.
I will also add that the developer of Slyedit is *VERY* responsive to any reported problems, with that app or any of the others that he has made. Not sure what gitlab would have to do with that; you seem quite confused about several different things. Hope you get it figured out.
firefox and myself were
commenting with each other on gitlab and it gets forwarded to here.. so
kk4qbn wrote to Gamgee <=-
On the other hand, gitlab, or the Developer of SlyEdit cannot really help
with the issues you have, so maybe you need to find a different venue to
vent your frustrations..
Huh? Vent my frustrations? Not following you here. I don't have any frustrations, and my editors all work.
Ok, wo this message really had nothing to do with you then did
it?? and you really did'nt offer ANY help on the subject DID YOU?
So WHY did you even comment??
I will also add that the developer of Slyedit is *VERY* responsive to any reported problems, with that app or any of the others that he has made. Not sure what gitlab would have to do with that; you seem quite confused about several different things. Hope you get it figured out.
DUDE.. WTF is your problem??? why are you even commenting to me..
this was an issue on gitlab that has nothing to do with you.. I
didnt ask for your comment or feedback.. for the most part I know
wtf I am doing I do have issues from time to time.. and I do like
to report issues that come up with stuff from time to time.. i've
been building Synchronet since 2005 or so under freebsd and linux
and don't really need your "Help"
Thats why I said that obviously you venting your frustrations
againsts something because I wasnt even commenting on here,
firefox and myself were commenting with each other on gitlab and
it gets forwarded to here.. so again.. what is you major
malfunction??
I don't care to say when I am wrong.. I'm the first to own my
shit. unlike a lot of people that the BBS hobby seems to
attract.. so why are you even commenting on this? it was done and
over.. there were no issue.. there was no problems until you just
created one..
and just because you have something setup one way does'nt mean it
is the CORRECT way..
just leave me alone... shit.. I just want to
peacefully run my bbs without "better than thou" shit don't stink
people coming up and trying to give me hell at every time I make
a "mistake"..
go away...
firefox and myself were
commenting with each other on gitlab and it gets forwarded to here.. so
*Nightfox
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 191:26:07 |
Calls: | 184 |
Calls today: | 1 |
Files: | 5,413 |
Messages: | 222,758 |