WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki
« previous next »
Pages: [1]   Go Down

Author Topic: "editor" not starting  (Read 5076 times)

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
"editor" not starting
« on: February 22, 2016, 05:32:16 AM »
Hi
because I think in path /usr/bin is after /usr/local/bin
Logged
dCore user

Offline nitram

  • Hero Member
  • *****
  • Posts: 1054
Re: "editor" not starting
« Reply #1 on: February 22, 2016, 07:14:06 AM »
The built-in editor starts OK on my dCore-jessie from menu or CLI.
Logged

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: "editor" not starting
« Reply #2 on: February 22, 2016, 04:28:37 PM »
jls - is this the Debian editor alternative?  I get the /usr/local/bin/editor from prebuilt Xprogs.  Of course, the /usr/local priority is a TC standard, but perhaps interferes with Debian's alternatives.
Logged

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: "editor" not starting
« Reply #3 on: February 22, 2016, 05:04:19 PM »
yes
Logged
dCore user

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: "editor" not starting
« Reply #4 on: February 22, 2016, 08:03:55 PM »
Ok, so we have a conundrum, placing /usr/local ahead of /usr/bin.  I will let folks give their opinion as to how we deal with this, Debian packages versus Tinycore ones in /usr/local.  The Tinycore apps are available by the FLTK graphical utilities and those that use them most likely do it by the graphical apps rather than the command line. 
Logged

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: "editor" not starting
« Reply #5 on: February 24, 2016, 02:34:25 PM »
As the prebuilt dCore section is very static but for kernel module updates, I think we are ok to place /usr/bin ahead of /usr/local.  Any possible file collisions in the future, the burden will be on the prebuilt section not to collide.  Any packages in Debian that need to be superceded by prebuilt, that can be done by blocking the Debian package and/or uploading a prebuilt one as prebuilt is found first by design ahead of any DEBINX, so the /usr/local path precedence is not needed.   Apps like fltk editor can have a .desktop file to allow them to easily be launched by menu. 

If this sounds agreeable, will apply on next RC.
Logged

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: "editor" not starting
« Reply #6 on: February 24, 2016, 05:14:32 PM »
Hi
I don't understand what's the needed change synce on my system debian editor already starts instead of the Xprogs one. maybe my .profile ( where I think the PATH variable is setted ) is different from the one in /etc/skel?
ps. I'm not on the pc right now
Logged
dCore user

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: "editor" not starting
« Reply #7 on: February 24, 2016, 10:39:31 PM »
As nothing has changed, /usr/local/bin/editor should be launched with issuing "editor". But planning to change that if no objection to having /usr/bin ahead of /usr/local/bin in $PATH.
Logged

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: "editor" not starting
« Reply #8 on: February 27, 2016, 07:43:57 PM »
The FLTK editor app in Xprogs has been renamed to /usr/local/bin/fltk-editor.
Logged

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11621
Re: "editor" not starting
« Reply #9 on: February 27, 2016, 08:13:48 PM »
Hi Jason W
Did you update the  .desktop  file too?
Logged

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: "editor" not starting
« Reply #10 on: February 27, 2016, 08:54:21 PM »
Oops, no, fixed it now and uploading.  Thanks for pointing it out.
Logged
Pages: [1]   Go Up
« previous next »