Re: locate question

On Wed, Nov 08, 2023 at 05:16:26PM +0100, to...@tuxteam.de wrote: > On Wed, Nov 08, 2023 at 11:45:30AM -0400, Roy J. Tellason, Sr. wrote: > > On Tuesday 07 November 2023 11:32:21 am gene heskett wrote: > > > so locate isn't working as I think it should. > > > try fin

Re: locate question

On Wed, Nov 08, 2023 at 11:45:30AM -0400, Roy J. Tellason, Sr. wrote: > On Tuesday 07 November 2023 11:32:21 am gene heskett wrote: > > so locate isn't working as I think it should. > > try find but it finds the whole my whole local net: > > gene@coyote:~$ find .scad .  |w

Re: locate question

On Tuesday 07 November 2023 11:32:21 am gene heskett wrote: > so locate isn't working as I think it should. > try find but it finds the whole my whole local net: > gene@coyote:~$ find .scad .  |wc -l > find: ‘.scad’: No such file or directory Try putting a * before the period in that

Re: locate question

If you just want to see files in /home/gene try locate -r 'home/gene/.*\.scad' In that way, regex syntax can be used to narrow down the search. Regards, Jörg.

Re: locate question

On 11/7/23 14:38, to...@tuxteam.de wrote: On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote: Greetings all; [...] gene@coyote:~$ locate *.scad /home/gene/vac_ctrl_box.scad /home/gene/xhome_cable.scad Markus and The Wanderer were spot on. As a reminder to all: this "

Re: locate question

its subs with assorted names ending in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an xfce t

Re: locate question

and all its subs with assorted names ending in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an

Re: locate question

On Tue, Nov 07, 2023 at 08:38:51PM +0100, to...@tuxteam.de wrote: > On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote: > > gene@coyote:~$ locate *.scad > > /home/gene/vac_ctrl_box.scad > > /home/gene/xhome_cable.scad > > Markus and The Wanderer were spot on

Re: locate question

On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote: > Greetings all; [...] > gene@coyote:~$ locate *.scad > /home/gene/vac_ctrl_box.scad > /home/gene/xhome_cable.scad Markus and The Wanderer were spot on. As a reminder to all: this "naked" *.scad gets already

Re: locate question

in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an xfce terminal but I get: gene@coyote:~$ locate *.sca

Re: locate question

subs with assorted names ending in ".scad", made by OpenSCAD > Fact: I just ran "sudo updatedb" and generated a new date just now, > /var/cache/locate/locatedb.n > so that s/b uptodate. > Al of those files should be spit out by: > "locate *.scad" is

Re: locate question

subs with assorted names ending in ".scad", made by OpenSCAD > Fact: I just ran "sudo updatedb" and generated a new date just now, > /var/cache/locate/locatedb.n > so that s/b uptodate. > Al of those files should be spit out by: > "locate *.scad" issued fr

Re: locate question

in ".scad", made by OpenSCAD Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an xfce terminal but I get: gene@coyo

locate question

D Fact: I just ran "sudo updatedb" and generated a new date just now, /var/cache/locate/locatedb.n so that s/b uptodate. Al of those files should be spit out by: "locate *.scad" issued from an xfce terminal but I get: gene@coyote:~$ locate *.scad /home/gene/vac_ctrl_box.scad /h

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

On Sun, Aug 27, 2023 at 02:17:06PM -0400, Jeffrey Walton wrote: [...] > The symlink tool works great, too: > > symlink -r / | grep dangling > > You can also delete them, once you verify they are dangling: > > symlink -r -d / > > In fact, it is a recommended post-upgrade step for

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

On Sun, Aug 27, 2023 at 1:10 PM Jörg-Volker Peetz wrote: > > to...@tuxteam.de wrote on 24/08/2023 14:00: > > > > A couple of days ago I was searching for dangling symlinks. > > > >find . -follow -lname "*" > > > How about > find -L . -type l The symlink tool works great, too:

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

On Sun, Aug 27, 2023 at 07:09:36PM +0200, Jörg-Volker Peetz wrote: > to...@tuxteam.de wrote on 24/08/2023 14:00: > > > > A couple of days ago I was searching for dangling symlinks. > > > >find . -follow -lname "*" > > > How about >find -L . -type l Should work, too. Cheers -- t

dangling symlinks [ was: Re: "locate" easier to use than "find"]

to...@tuxteam.de wrote on 24/08/2023 14:00: A couple of days ago I was searching for dangling symlinks. find . -follow -lname "*" How about find -L . -type l Regards, Jörg.

Re: "locate" easier to use than "find"

> > to...@tuxteam.de (12023-08-24): > > > Dunno. I use find nearly every day. Seeing it as "just a recursive > > > grep" doesn't cover a fraction of its usefulness. > > > > > > A couple of days ago I was searching for dangling symlinks. > > > > > > find . -follow -lname "*" Wow... what a

Re: "locate" easier to use than "find"

Stanislav Vlasov (12023-08-24): > Sometimes it's unexpected :-) Then the shell prints an error and I try again. Still less time wasted than these two mails. Regards, -- Nicolas George

Re: "locate" easier to use than "find"

чт, 24 авг. 2023 г. в 18:17, Nicolas George : > > With a really large amount of files there will be overflow of process > > environment (or too large cmdline). > If I expect a very large amount of files, I can use it another way. Sometimes it's unexpected :-) -- Stanislav

Re: "locate" easier to use than "find"

I was searching for dangling symlinks. > > > > find . -follow -lname "*" > > ls **/*(N@-@) > > Zsh rulz. Definitely. My point was rather to illustrate the kind of things find can do that locate can't. There is more than one way to do it (TM). Cheers -- t signature.asc Description: PGP signature

Re: "locate" easier to use than "find"

Stanislav Vlasov (12023-08-24): > With a really large amount of files there will be overflow of process > environment (or too large cmdline). If I expect a very large amount of files, I can use it another way. -- Nicolas George

Re: "locate" easier to use than "find"

ng for dangling symlinks. > > > > find . -follow -lname "*" > > ls **/*(N@-@) With a really large amount of files there will be overflow of process environment (or too large cmdline). locate and find does not store filenames in memory. -- Stanislav

Re: "locate" easier to use than "find"

to...@tuxteam.de (12023-08-24): > Dunno. I use find nearly every day. Seeing it as "just a recursive > grep" doesn't cover a fraction of its usefulness. > > A couple of days ago I was searching for dangling symlinks. > > find . -follow -lname "*" ls **/*(N@-@) Zsh rulz. Regards, --

Re: "locate" easier to use than "find"

On Thu, Aug 24, 2023 at 01:52:28PM +0200, Oliver Schoede wrote: [...] > Have basically stopped using traditional 'find' outside of scripts, as > always thought I was about the last one [...] Dunno. I use find nearly every day. Seeing it as "just a recursive grep" doesn't cover a fraction of its

Re: "locate" easier to use than "find"

ug >> > 21 13:29 .mozilla/firefox/gs0gkgv2.default/favicons.sqlite 1515049 >> >    260 -rw-r--r--   1 myusername myusername   262144 Aug 18 22:36 >> > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite >> >> For me command "locate" is easier t

Re: "locate" easier to use than "find"

On Mon, Aug 21, 2023 at 06:45:16PM +0100, Brian wrote: [...] > plocate-updatedb.service and plocate-updatedb.timer take care of > that for me. :) I admit to accepting some help from trusty cron :) > > Tools, jobs and that :) > > Indeed. Cheers -- t signature.asc Description: PGP signature

Re: "locate" easier to use than "find"

On 2023-08-21 17:21, to...@tuxteam.de wrote: On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote: On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de: >> For me command "locate" is easier to use than "find": > > They do different things. Locate i

Re: "locate" easier to use than "find"

On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote: > On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de: > >> For me command "locate" is easier to use than "find": > > > > They do different things. Locate is much faster, but it only l

Re: "locate" easier to use than "find"

On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de: >> For me command "locate" is easier to use than "find": > > They do different things. Locate is much faster, but it only looks > into file names. Find can do nearly everything, like looking into > file met

Re: "locate" easier to use than "find"

lite > >  1515049    260 -rw-r--r--   1 myusername myusername   262144 Aug 18 22:36 > > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite > > For me command "locate" is easier to use than "find": They do different things. Locate is much faster, bu

"locate" easier to use than "find"

/th3dv2jy.default-1461749950404/favicons.sqlite For me command "locate" is easier to use than "find": rprice@titan ~ locate favicons.sqlite /mnt/home/rprice/.mozilla/firefox/60mahk24.default-esr/favicons.sqlite /mnt/home/rprice/.mozilla/firefox/60mahk24.default-esr/favicons.

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On Fri, Jul 08, 2022 at 08:37:19AM -0500, Albretch Mueller wrote: > [...] that bash utils needed to be declared in > the PATH in order for you to access them. Noticing it and opening > another windows was all it took. Ah, oh. You overwrote your PATH. Makes sense now :) > it amazes me also how

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On Fri, 2022-07-08 at 08:37 -0500, Albretch Mueller wrote: > it seemed to have been somehow > blanketed by my "unconscious" that bash utils needed to be declared in > the PATH in order for you to access them. 'which' isn't a 'bash util' whatever that is (presumably you mean a shell built-in). As

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

after reading through all your suggestions and still wondering about what exactly was the mistake that I had made, I realized that it was a simple and stupid "type in a rush and let 'the compiler' (sorry!) find the mistake for you" kind of error: it seemed to have been somehow blanketed by my

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On 2022-07-08 12:48, Greg Wooledge wrote: https://wiki.debian.org/DebianAlternatives thanks mick

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

* The problem happens in all terminals I've tried -- xterm, rxvt-unicode, gnome-terminal and konsole. * If I type 'zsh' the problem goes away. But I really want it to work in bash too. * I did a 'locate cat' and I can see that it's in /usr/bin, or at least locate thinks it is. Here is the output of 'ls -l /usr/bin/cat'.

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On 2022-07-08 at 07:48, Greg Wooledge wrote: > On Fri, Jul 08, 2022 at 12:47:19PM +0100, mick crane wrote: > >> here on bookworm >> mick@pumpkin:~$ ls -la /usr/bin |grep which >> lrwxrwxrwx 1 root root 23 Jan 23 18:05 which -> >> /etc/alternatives/which >> -rwxr-xr-x 1 root root

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On Fri, Jul 08, 2022 at 12:47:19PM +0100, mick crane wrote: > here on bookworm > mick@pumpkin:~$ ls -la /usr/bin |grep which > lrwxrwxrwx 1 root root 23 Jan 23 18:05 which -> > /etc/alternatives/which > -rwxr-xr-x 1 root root 946 May 1 17:47 which.debianutils > mick@pumpkin:~$

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

On 2022-07-08 11:30, to...@tuxteam.de wrote: Not every binary is contained in a package called like it. That's what "apt-file" is for (in the same named package): tomas@trotzki:~$ apt-file search bin/which debian-goodies: /usr/bin/which-pkg-broke debian-goodies:

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

h anything else that's in this message. > export _GRAALVM_HOME=.../graalvm-ce-java17-22.1.0 > export PATH=${PATH}:${_GRAALVM_HOME}/bin > which javac > which java > $ > > bash: which: command not found > > # apt-get install which > Reading package lists... Done > Building

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

check what $PATH contains? (e.g. echo $PATH) It seems likely it's corrupted or missing the right directory (/usr/bin see below). > > # apt-get install which > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > E: Unable to loc

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

> Building dependency tree... Done > Reading state information... Done > E: Unable to locate package which > # > > > > # cat /etc/apt/sources.list > # deb cdrom:[Official Debian GNU/Linux Live 11.2.0 lxde > 2021-12-18T12:41]/ bullseye main > #deb cd

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

.1.0 > export PATH=${PATH}:${_GRAALVM_HOME}/bin > which javac > which java > $ > > bash: which: command not found > > # apt-get install which > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > E: Unable to loca

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

which has been deprecated. Use command -v. If you need which -a, you are out of luck... Please find an attached which if you are interested. # apt-get install which > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > E: Unable to

Re: bash: which: command not found? + (E: Unable to locate package which? ...)

Hi, Albretch Mueller wrote: > # apt-get install which > E: Unable to locate package which Try apt-get install debianutils I got the proposal from $ apt-file search which | grep 'which$' | less which still finds 18 lines which end by "which". Number two looks like the

bash: which: command not found? + (E: Unable to locate package which? ...)

${_GRAALVM_HOME}/bin which javac which java $ bash: which: command not found # apt-get install which Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package which # # cat /etc/apt/sources.list # deb cdrom:[Official Debian G

Re: Help with --regex in locate

ash' changed from 0640 (rw-r-) to 0740 (rwxr-) > > Now we have created a command that just > displays the arguments that it receives from > the shell. > > The command is in the current directory > and not in the PATH, so we need to specify > its location when in

Re: Help with --regex in locate

we have created a command that just displays the arguments that it receives from the shell. The command is in the current directory and not in the PATH, so we need to specify its location when invoking it: ./show_args.bash Here's what it shows for a couple of commands that you had trouble with.

Re: Metavariable [was: Help with --regex in locate]

On Tue, Dec 03, 2019 at 10:18:59AM -0500, Stefan Monnier wrote: > > I think the canonical name is "metasyntactic variable" [1]. I've > > seen also just "metavariable", although Wikipedia would say that > > the latter belongs in the realm of logic [2], not programming. > > AFAICT those two usages

Re: Metavariable [was: Help with --regex in locate]

> I think the canonical name is "metasyntactic variable" [1]. I've > seen also just "metavariable", although Wikipedia would say that > the latter belongs in the realm of logic [2], not programming. AFAICT those two usages are one and the same: when you see "foo" it's because the code is actually

Re: Help with --regex in locate

On Ma, 03 dec 19, 15:09:45, Jonas Smedegaard wrote: > > What I have so far settled on is to distinguish "variables" in capital > letters, and explicitly hint that it should be changed, like this: > > With 'find' instead of 'locate' (adapt dir): > > find DI

Metavariable [was: Help with --regex in locate]

On Tue, Dec 03, 2019 at 08:07:16AM -0500, rhkra...@gmail.com wrote: [...] > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > With 'find' instead of 'locate'. [...] > It took me a minute (well, a trial) to realize that dir_with_repos is a > metaname (right wo

Re: Help with --regex in locate

On Tuesday, December 03, 2019 09:01:16 AM Greg Wooledge wrote: > On Tue, Dec 03, 2019 at 05:54:33AM -0500, Rh Kramer wrote: > > locate --regex \/\.gitignore > > Your quoting is all wrong here. What you want is: > > locate --regex '/\.gitignore' > > The / does no

Re: Help with --regex in locate

On Tuesday, December 03, 2019 09:09:45 AM Jonas Smedegaard wrote: > With 'find' instead of 'locate' (adapt dir): > > find DIR_WITH_REPOS -type d -name .git That helps, also, especially with the note "adapt dir" (or maybe "adjust dir", or "specify dir ap

Re: Help with --regex in locate

On Tuesday, December 03, 2019 08:39:28 AM Brian wrote: > On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote: > > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > > With 'find' instead of 'locate'. > > > > > > fi

Re: Help with --regex in locate

Quoting Brian (2019-12-03 14:39:28) > On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote: > > > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > > With 'find' instead of 'locate'. > > > > > >

Re: Help with --regex in locate

On Tue, Dec 03, 2019 at 05:54:33AM -0500, Rh Kramer wrote: > locate --regex \/\.gitignore Your quoting is all wrong here. What you want is: locate --regex '/\.gitignore' The / does not need to be quoted, either for the shell, or for the regex. It's just a regular old character with no spec

Re: Help with --regex in locate

On Tue 03 Dec 2019 at 08:07:16 -0500, rhkra...@gmail.com wrote: > On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > > With 'find' instead of 'locate'. > > > > find dir_with_repos -type d -name .git > > > > or > > > >

Re: Help with --regex in locate

Andrei, Thanks very much! (Please forgive the nitpicky comment below.) On Tuesday, December 03, 2019 07:16:22 AM Andrei POPESCU wrote: > With 'find' instead of 'locate'. > > find dir_with_repos -type d -name .git > > or > > find dir_with_repos -type d -name &qu

Re: Help with --regex in locate

't mind other approaches, especially if they are simpler, I > would like to learn what I'm doing wrong with locate --regex. With 'find' instead of 'locate'. find dir_with_repos -type d -name .git or find dir_with_repos -type d -name "*.git" if you also have git bare cl

Resolved: Re: Help with --regex in locate

ally if they are simpler, I > would like to learn what I'm doing wrong with locate --regex. > > Overall objective: > > I have several .git repositories on this computer. I want to get a list of > those repositories without getting a listing of all the files in each > repos

Help with --regex in locate

I'm doing wrong with locate --regex. Overall objective: I have several .git repositories on this computer. I want to get a list of those repositories without getting a listing of all the files in each repository. Each repository is in a different subdirectory, and with varying path lengths

Re: Problem to locate bug

Hi Julian, Quoting sj...@uranus.uni-freiburg.de (2019-11-21 11:39:14) > if it (from around June 28th) still matters for somebody: I > re-installed my whole system and I couldn't re-recognise the behaviour > described. I also can't remember having changed anything in the > "deeper settings of

Re: Problem to locate bug

Hi, if it (from around June 28th) still matters for somebody: I re-installed my whole system and I couldn't re-recognise the behaviour described. I also can't remember having changed anything in the "deeper settings of the system"… However, best regards, Julian Schreck -- > Hi, > > Julian

Re: Problem to locate bug

Hi, I tried to shut down the pc with ctrl + alt + 1 -> [login] -> sudo poweroff -> no reaction. I had some music file playing. A snippet (< 1 s) was repeated roughly between 5 and 10 times before I didn't hear anything further on. Ctrl + SysRq + k normally reboot immediately. In my case, no

Re: Problem to locate bug

Hi, Julian Schreck wrote: > I could narrow it down to lxterminal (autostarted), You could start another terminal program from the lxterminal and then end the lxterminal. (I use "xterm", the old and sparse one.) You could also check whether the lxterm menus give you an opportunity to disable any

Re: Problem to locate bug

Hi, I could narrow it down to lxterminal (autostarted), openbox or an automatically started process. Any other advice than changing the window manager (in case that was suggested/your intention)? - A rough description of the kind of computer: ”# lshw“ gives debian

Re: Problem to locate bug

On 6/24/19 6:52 AM, sj...@uranus.uni-freiburg.de wrote: Dear all, for some weeks (or months perhaps already), my screen freezes suddenly and once in a while without any chance to de-freeze it again. I don't know wether my input is recognized after such a freeze, but I don't think so. (I

Re: Problem to locate bug

Hi, sj...@uranus.uni-freiburg.de wrote: > As far as I can see, this behaviour may only be > caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution, > openbox. Consider to use alternatives for a few days until it is clear whether avoiding one or more of the suspects makes the

Problem to locate bug

Dear all, for some weeks (or months perhaps already), my screen freezes suddenly and once in a while without any chance to de-freeze it again. I don't know wether my input is recognized after such a freeze, but I don't think so. (I should've tested this before writing to you…) The thing is that

Re: E: Unable to locate package zimlib . . .

On 25.01.2019 1:15, Albretch Mueller wrote: > I installed the package, but could not make sense of it. > > "zim" is the extension used by compressed wikipedia pages. You find > such files here: > > https://wiki.kiwix.org/wiki/Content > http://download.kiwix.org/zim/wikipedia_en_all_nopic.zim >

Re: E: Unable to locate package zimlib . . .

On 1/16/19, Tom Bachreier wrote: > I don't know what zimlib is but you mean maybe libzim? In stretch is > libzim0v5: > I installed the package, but could not make sense of it. "zim" is the extension used by compressed wikipedia pages. You find

Re: E: Unable to locate package zimlib . . .

Hi! Jan 16, 2019, 8:00 AM by lbrt...@gmail.com: > Why is it I can't install zimlib? > I don't know what zimlib is but you mean maybe libzim? In stretch is libzim0v5: Tom

Re: E: Unable to locate package zimlib . . .

https://packages.debian.org/sid/xz-utils seems to be what I actually needed in order to decompress zim files

Re: E: Unable to locate package zimlib . . .

> Why is it I can't install zimlib? Because there is no package named zimlib available: https://packages.debian.org/search?keywords=zimlib You probably want libzim-dev, which does exist: https://packages.debian.org/search?keywords=libzim Note that libzim 2.x is only available

E: Unable to locate package zimlib . . .

Why is it I can't install zimlib? # apt-get install zimlib Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package zimlib # apt-get update Get:1 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB] Ign:2 http

Re: fonction find ou locate en mode graphique

Le 24/11/2018 à 05:39, Bernard Schoenacker a écrit : Bonjour, Si c'est pour le gestionnaire Thunar, catfish installé Il suffit d'aller dans le menu Édition Configurer Actions personnalisées ajouter une action l’icône + - Nom = Recherche - Description = Effectuer une recherche - Commande =

Re: fonction find ou locate en mode graphique

taper updatedb (sur mon portable, ça prend 6 secondes) locate blabla | grep /home/meme de plus, je dois être plus nul que la mémé lambda, car je ne comprends pas ce que j'obtiens: malgré la ligne "Path=$HOME", il m'affiche des fichiers sur tous mes disques. Cordialement, -- Pierre Frenkiel

Re: fonction find ou locate en mode graphique

Salut Harico, Merci pour ta longue et détaillée réponse. Le 23-11-2018, à 15:54:38 +0100, Haricophile a écrit : Le Fri, 23 Nov 2018 14:54:27 +0100, steve a écrit : Pour rebondir à ce sujet, je cherche (sans vraiment chercher) un bon moyen de chercher dans des pdf avec une vue des

Re: fonction find ou locate en mode graphique

- Mail original - > De: "hamster" > À: debian-user-french@lists.debian.org > Envoyé: Samedi 24 Novembre 2018 00:35:37 > Objet: Re: fonction find ou locate en mode graphique > > Le 23/11/2018 à 10:03, Pierre Frenkiel a écrit : > > Oh oui, il arrive q

Re: fonction find ou locate en mode graphique

ir les préférences de firefox et voir ou est l'endroit par défaut… mais ca c'est des choses que les utilisateurs un minimum formés savent faire. Pas les autres. >   A quoi sert le grep? "locate /home/user" suffit.. Ah, je connaissait pas cet usage de locate. Merci pour le tuyau. &g

Re: fonction find ou locate en mode graphique

Le Fri, 23 Nov 2018 14:54:27 +0100, steve a écrit : > Pour rebondir à ce sujet, je cherche (sans vraiment chercher) un bon > moyen de chercher dans des pdf avec une vue des résultats pas trop > rébarbatives et configurable si possible. > > Si quelqu'un dans la salle a une suggestion, je suis

Re: fonction find ou locate en mode graphique

Le 23-11-2018, à 16:11:37 +0100, Klaus Becker a écrit : il y a pdfgrep. Pour la sortie, on peut éventuellement se faire un petit script, je l'ai fait pour mes besoins. Cool, ça marche bien. C'est en ligne de commandes. Un plus. Merci !

Re: fonction find ou locate en mode graphique

Le 23/11/2018 à 14:54, steve a écrit : Le 23-11-2018, à 13:44:59 +0100, Haricophile a écrit : Pour chercher dans le contenu fichiers je ne connais rien qui ne bouffe pas plein de ressources système a un moment ou un autre. Il y a bien Gnome Tracker... mais il n'y a plus d'interface propre,

Re: fonction find ou locate en mode graphique

Le 23-11-2018, à 13:44:59 +0100, Haricophile a écrit : Pour chercher dans le contenu fichiers je ne connais rien qui ne bouffe pas plein de ressources système a un moment ou un autre. Il y a bien Gnome Tracker... mais il n'y a plus d'interface propre, il me semble que Nautilus l'utilise

Re: fonction find ou locate en mode graphique

Le Thu, 22 Nov 2018 21:51:17 +0100 (CET), Bernard Schoenacker a écrit : > bonjour, > > si possible en gtk3 > > merci > slt > bernard Si c'est juste sur les noms de fichier, catfish est léger et performant. Il commence par utiliser mlocate pour aller vite, et cherche plus avant. Tu peux

Re: fonction find ou locate en mode graphique

Hello, En mode graphique je ne sais pas. En mode console : # updatedb # locate Rien ne vaut le mode console :-) A. Valmer

Re: fonction find ou locate en mode graphique

On Fri, 23 Nov 2018, hamster wrote: Il faut comparer ce qui est comparable. Locate ne cherche pas sur le disque mais dans une base de données. Ca te sort donc des résultats correspondant a l'état du disque la dernière fois que la base de donnés a été mise a jour. Pour avoir des résultats a jour

Re: fonction find ou locate en mode graphique

Le 23/11/2018 à 08:43, Pierre Frenkiel a écrit : > On Thu, 22 Nov 2018, Klaus Becker wrote: > >> kfind - utilitaire de recherche de fichiers > >   Il me semble assez nul: >   avec "locate profile", j'ai 5453 résultats en 10 secondes. >   avec kfind, il faut

Re: fonction find ou locate en mode graphique

On Thu, 22 Nov 2018, Klaus Becker wrote: kfind - utilitaire de recherche de fichiers Il me semble assez nul: avec "locate profile", j'ai 5453 résultats en 10 secondes. avec kfind, il faut se placer sur / avant de le lancer, et en cherchant "profile", j'ai 30 r

Re: fonction find ou locate en mode graphique

Le 22/11/2018 à 21:00, Bernard Schoenacker a écrit : bonjour, j'ai une mémé qui souhaite passer à linux mais elle tiend à "son exploseur windows" et à sa fonction de recherche en mode graphique ... désolé, mais j'y ai jamais songé ... quelle est la bonne attitude ? merci slt bernard Slt,

Re: fonction find ou locate en mode graphique

Le gestionnaire de fichiers PCmanFM possède une fonction de recherche de fichiers. -- Gérard

Re: fonction find ou locate en mode graphique

Le 22/11/2018 à 20:50, Bernard Schoenacker a écrit : > bonjour, > > j'ai une mémé qui souhaite passer à linux > mais elle tiend à "son exploseur windows" > et à sa fonction de recherche en mode > graphique ... > > désolé, mais j'y ai jamais songé ... > > quelle est la bonne attitude ? Les

Re: fonction find ou locate en mode graphique

exploseur ? exploreur ? Virtual box comme ça si elle regrette elle pourra reprendre windaube Le 22/11/2018 à 20:50, Bernard Schoenacker a écrit : bonjour, j'ai une mémé qui souhaite passer à linux mais elle tiend à "son exploseur windows" et à sa fonction de recherche en mode graphique ...

Re: fonction find ou locate en mode graphique

- Mail original - > De: "Klaus Becker" > À: debian-user-french@lists.debian.org > Envoyé: Jeudi 22 Novembre 2018 21:34:07 > Objet: Re: fonction find ou locate en mode graphique > > Le 22/11/2018 à 20:50, Bernard Schoenacker a écrit : > > $ ap

Re: fonction find ou locate en mode graphique

Le 22 novembre 2018 21:34:07 GMT+01:00, Klaus Becker a écrit : > > >Le 22/11/2018 à 20:50, Bernard Schoenacker a écrit : >> bonjour, >> >> j'ai une mémé qui souhaite passer à linux >> mais elle tiend à "son exploseur windows" >> et à sa fonction de recherche en mode >> graphique ... >> >>

Re: fonction find ou locate en mode graphique

Le 22/11/2018 à 20:50, Bernard Schoenacker a écrit : bonjour, j'ai une mémé qui souhaite passer à linux mais elle tiend à "son exploseur windows" et à sa fonction de recherche en mode graphique ... désolé, mais j'y ai jamais songé ... quelle est la bonne attitude ? merci slt bernard $

fonction find ou locate en mode graphique

bonjour, j'ai une mémé qui souhaite passer à linux mais elle tiend à "son exploseur windows" et à sa fonction de recherche en mode graphique ... désolé, mais j'y ai jamais songé ... quelle est la bonne attitude ? merci slt bernard

  1   2   3   4   5   6   >