When after log in, I type ~/tdsr/tdsr that works. > On Oct 7, 2022, at 10:29, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: > > Try manually executing the script to find out if you get an error. > > '. .bash_login' > > Maybe it could be a permissions problem or a typo etc. > > > > On 10/7/2022 11:03 AM, Linux for blind general discussion wrote: >> Both .bash_profile and .bash_login were tried, adding >> ~/tdsr/tdsr >> and tdsr did not start. >> What next? >> >>> On Oct 6, 2022, at 14:40, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>> >>> Thanks, will try that. >>> >>>> On Oct 6, 2022, at 14:09, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>> >>>> The ./ command is not necessary since the ~/tdsr/tdsr runs the program. >>>> >>>> >>>> Ryan Mann >>>> Certified Assistive Technology Instructional Specialist >>>> rmann0581@xxxxxxxxx >>>> 386-383-5175 >>>> >>>> >>>>> On Oct 6, 2022, at 3:04 PM, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>> >>>>> Then what about the command >>>>> ./tdsr >>>>> or does that you suggest take care of the dot slash command? >>>>> >>>>>> On Oct 6, 2022, at 11:15, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>>> >>>>>> Typing ~/tdsr/tdsr gives the direct path to the file. That way the system knows where tdsr is without you needing to cd to the directory. >>>>>> >>>>>> >>>>>> Ryan Mann >>>>>> Certified Assistive Technology Instructional Specialist >>>>>> rmann0581@xxxxxxxxx >>>>>> 386-383-5175 >>>>>> >>>>>> >>>>>>>> On Oct 6, 2022, at 12:12 PM, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>>>> Since tdsr is started by using >>>>>>> ./tdsr >>>>>>> from within >>>>>>> /tdsr, how is this done using >>>>>>> ~/tdsr/tdsr >>>>>>> >>>>>>>> On Oct 6, 2022, at 10:48, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>>>>> >>>>>>>> You can try it the way you show, or just specify the path to the 'tdsr' executable like '~/tdsr/tdsr' or '/home/xxxxx/tdsr/tdsr' instead of 'cd' to the directory. Once you create the file, log out and back in to test if the TDSR starts automatically. >>>>>>>> >>>>>>>> >>>>>>>>> On 10/6/2022 9:53 AM, Linux for blind general discussion wrote: >>>>>>>>> And do that using >>>>>>>>> nano .bash_login >>>>>>>>> and write >>>>>>>>> cd tdsr >>>>>>>>> ./tdsr >>>>>>>>> cd .. >>>>>>>>> Is that it? >>>>>>>>> >>>>>>>>>> On Oct 6, 2022, at 08:48, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>>>>>>> >>>>>>>>>> Just create the file. >>>>>>>>>> >>>>>>>>>> On 10/5/2022 5:31 PM, Linux for blind general discussion wrote: >>>>>>>>>>> Using ls .bash_login >>>>>>>>>>> and sudo ls .bash_login >>>>>>>>>>> I am not finding that file. >>>>>>>>>>> I am in the home directory. >>>>>>>>>>> Am I doing something wrong? >>>>>>>>>>> >>>>>>>>>>>> On Oct 5, 2022, at 08:37, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>>>>>>>>> >>>>>>>>>>>> If 'bash' is your login shell, try adding the TDSR startup command to .bash_login in your home directory. That should avoid the problems Tim indicated when a subshell is invoked. >>>>>>>>>>>> >>>>>>>>>>>> You may have to create that file if it doesn't exist. It is documented in the 'bash' manual page. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 10/5/2022 1:17 AM, Linux for blind general discussion wrote: >>>>>>>>>>>>> Or might it be easier to install espeakup, or install Fenrir? >>>>>>>>>>>>> I welcome anyone's ideas. >>>>>>>>>>>>> >>>>>>>>>>>>>> On Oct 4, 2022, at 15:31, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Maybe better to keep logging in, go to cd tdsr, >>>>>>>>>>>>>> then type >>>>>>>>>>>>>> ./tdsr >>>>>>>>>>>>>> cd .. >>>>>>>>>>>>>> as I already do. >>>>>>>>>>>>>> What you had written is far too advanced for me, but thank you. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Oct 4, 2022, at 08:46, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Tim here. It's a little tricky because, without additional >>>>>>>>>>>>>>> precautions, you open a shell which launches tdsr, which opens a >>>>>>>>>>>>>>> shell inside of it, which launches tdsr, which opens a shell >>>>>>>>>>>>>>> which...you get the idea. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So there needs to be a way for a shell to determine if it's already >>>>>>>>>>>>>>> inside a running session of tdsr. This sort of thing is usually >>>>>>>>>>>>>>> done through setting an environment variable. For example, I've >>>>>>>>>>>>>>> done similarly with "tmux", so I have a check in my startup file >>>>>>>>>>>>>>> (e.g. my ~/.bashrc) that tests >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [ -z "$TMUX" ] && tmux >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So first you'd want to see if tdsr sets an environment variable. >>>>>>>>>>>>>>> The documentation might detail this, but if not, you can dump the >>>>>>>>>>>>>>> environment to a file before running tdsr, then run tdsr, then dump >>>>>>>>>>>>>>> the environment to another file and compare them, like >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> $ env | sort > a >>>>>>>>>>>>>>> $ tdsr >>>>>>>>>>>>>>> (tdsr)$ env | sort > b >>>>>>>>>>>>>>> (tdsr)$ comm -13 a b >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hopefully this will show a setting something like a "$TDSR" variable >>>>>>>>>>>>>>> that you can check. Then your ~/.bashrc (or whatever your startup >>>>>>>>>>>>>>> file is) can end with something like >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [ -z "$TDSR" ] && tdsr >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Because this can go unfortunately sideways, I recommend having one >>>>>>>>>>>>>>> window/console open, editing your ~/.bashrc and then open a *new* >>>>>>>>>>>>>>> window (or log in at another console) to test it. If all goes >>>>>>>>>>>>>>> right, yay. If things go sideways, you can quickly flip back to >>>>>>>>>>>>>>> the first window/console, remove that line from your ~/.bashrc, and >>>>>>>>>>>>>>> (re)save it. This saves you a LOT of hassle if you accidentally >>>>>>>>>>>>>>> create a loop like described at the top of this email. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -Tim >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On 2022-10-04 08:21, Linux for blind general discussion wrote: >>>>>>>>>>>>>>>> I have fedora 35, and while in the shell I use tdsr for screen-reader. >>>>>>>>>>>>>>>> To start it, one must use dot slash tdsr. >>>>>>>>>>>>>>>> Is there a way to have this program start whenever logging in at shell? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Blinux-list mailing list >>>>>>>>>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Blinux-list mailing list >>>>>>>>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Blinux-list mailing list >>>>>>>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Blinux-list mailing list >>>>>>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Blinux-list mailing list >>>>>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Blinux-list mailing list >>>>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Blinux-list mailing list >>>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Blinux-list mailing list >>>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Blinux-list mailing list >>>>>>>> Blinux-list@xxxxxxxxxx >>>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>> _______________________________________________ >>>>>>> Blinux-list mailing list >>>>>>> Blinux-list@xxxxxxxxxx >>>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>>>> >>>>>> _______________________________________________ >>>>>> Blinux-list mailing list >>>>>> Blinux-list@xxxxxxxxxx >>>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>>> _______________________________________________ >>>>> Blinux-list mailing list >>>>> Blinux-list@xxxxxxxxxx >>>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>>> _______________________________________________ >>>> Blinux-list mailing list >>>> Blinux-list@xxxxxxxxxx >>>> https://listman.redhat.com/mailman/listinfo/blinux-list >>> _______________________________________________ >>> Blinux-list mailing list >>> Blinux-list@xxxxxxxxxx >>> https://listman.redhat.com/mailman/listinfo/blinux-list >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@xxxxxxxxxx >> https://listman.redhat.com/mailman/listinfo/blinux-list > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/blinux-list _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/blinux-list