Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #286727
| From | Karen Lewellen <klewellen@shellworld.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: a hopefully simple ls command question? |
| Date | 2026-05-17 07:30 +0200 |
| Message-ID | <MVCeB-5Kcg-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <MVmCS-5z7Q-9@gated-at.bofh.it> <MVsoV-5CXY-5@gated-at.bofh.it> <MVsRX-5Dqo-1@gated-at.bofh.it> <MVtO2-5E2T-11@gated-at.bofh.it> <MVCeB-5Kcg-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Hi David, This is not my desktop, with my not having permission to add software. I do thank you, and everyone else, for ideas. Speaking personally though, one thing I learned from all the options sort of underscores a long held stance of my own. If one wanted a hand clapping program in Linux, you would likely end up with three. one for the right, one for the left, and a third to make them clap smiles. At this stage, speaking personally, it might be faster for me to find the article again creating a new file and name. My main desktop uses DOS. For me, I could locate this with a simple single command...and I have been spoiled by the ease of ls -l when hunting through scores of things on my Linux shell services. Cheers all, Kare On Sat, 16 May 2026, David Wright wrote: > On Sat 16 May 2026 at 16:25:41 (-0400), Karen Lewellen wrote: >> Hi Greg, >> Thanks, I am aiming for solidity here. >> I am using a screen reader. >> The text editor wording is a bit confusing. >> Also, because I create many text files in a given day, my goal is very >> tight here, but it seems I cannot provide actual dates, just a number >> of days window? >> There is not a syntax for say the window of 12 may, say 5 days ago until >> 14 may, which would be 2 days ago? >> if I follow using . provides my home directory, where my files are >> stored, is that correct? This is not my desktop, but a service. >> I do understand that I should write say "*.txt" >> However I need to be sure I have corrected the mistake you noted, >> should it be namef with the dash character? >> Your extras with print seem profoundly complex. >> My goal is clear text, that my screen reader can manage, when I use >> its own review mode. >> Does that make more sense? >> My goals are very tight, as I want to locate a file I saved within >> this small window, with screen output that my talking computer >> manages. > > I use a bash function for this task. I've attached it as some of the > lines are a bit long. I have it in my ~/.bashrc, making it always > available. > > You can try it out by saving the attachment, and then typing: > > $ bash -c '. ./find-between; find-between today yesterday ./ | less' > > which will give you a list of recent files in this directory, > piped into less as there may be many files in the list. > > The function is documented, as can be seen by typing: > > $ bash -c '. ./find-between; find-between' > Usage: find-between timedate timedate top-of-trees … > finds files under top-of-trees with modification timestamps between > the two timedates given (free format, in any order; hint: '2000-12-31 11:59' > is a simple format that works). The output is sorted by filename. > $ > > If you add the find-between file to your .bashrc, then you only have > to type the function name: > > $ find-between > > $ find-between today yesterday ./ | less > > Obviously you would replace today and yesterday with real dates/times. > Their format is whatever is acceptable to date --d (see man date). > The order doesn't matter. > > All files are listed, but it's a simple matter to grep the outout: > > $ find-between today yesterday ./ | grep 'txt$' | less > > though you lose the header line as it's unlikely to match: > > From 2026-05-15 21:57:42-05:00 to 2026-05-16 21:57:42-05:00 > 20260516-081119.08 2136 .Xresources > [ … lots more filenames … ] > > [Aside: replace the echo commands if they offend you. > I have msgerr and msgout functions in their place.] > > Cheers, > David. >
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar
a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 06:00 +0200
Re: a hopefully simple ls command question? David Christensen <dpchrist@holgerdanske.com> - 2026-05-16 06:30 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 09:20 +0200
Re: a hopefully simple ls command question? debian-user@howorth.org.uk - 2026-05-16 12:20 +0200
Re: a hopefully simple ls command question? David Christensen <dpchrist@holgerdanske.com> - 2026-05-17 08:00 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-17 23:20 +0200
Re: a hopefully simple ls command question? Teemu Likonen <tlikonen@iki.fi> - 2026-05-16 07:00 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 09:20 +0200
Re: a hopefully simple ls command question? Dan Ritter <dsr@randomstring.org> - 2026-05-16 10:20 +0200
Re: a hopefully simple ls command question? Greg Wooledge <greg@wooledge.org> - 2026-05-16 14:50 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 22:30 +0200
Re: a hopefully simple ls command question? Greg Wooledge <greg@wooledge.org> - 2026-05-16 22:50 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 23:10 +0200
Re: a hopefully simple ls command question? debian-user@howorth.org.uk - 2026-05-17 18:40 +0200
Re: a hopefully simple ls command question? Dan Ritter <dsr@randomstring.org> - 2026-05-17 01:00 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-17 02:30 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-17 07:30 +0200
Re: a hopefully simple ls command question? John Hasler <john@sugarbit.com> - 2026-05-17 15:20 +0200
Re: a hopefully simple ls command question? John Hasler <john@sugarbit.com> - 2026-05-17 22:10 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-18 00:10 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-18 05:50 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-18 07:00 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-18 07:40 +0200
Re: a hopefully simple ls command question? David Wright <deblis@lionunicorn.co.uk> - 2026-05-18 05:30 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 22:40 +0200
Re: a hopefully simple ls command question? Chime Hart <chime@hubert-humphrey.com> - 2026-05-16 22:50 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 23:10 +0200
Re: a hopefully simple ls command question? CGS <etphonehomefrance@gmail.com> - 2026-05-17 16:40 +0200
Re: a hopefully simple ls command question? Karen Lewellen <klewellen@shellworld.net> - 2026-05-16 21:00 +0200
Re: a hopefully simple ls command question? Karl Vogel <vogelke+debian@pobox.com> - 2026-05-16 21:50 +0200
Re: a hopefully simple ls command question? Greg Wooledge <greg@wooledge.org> - 2026-05-16 21:30 +0200
Re: a hopefully simple ls command question? Andrew Latham <lathama@gmail.com> - 2026-05-16 21:30 +0200
csiph-web