[Deluge] #3646: deluge-gtk: ^F/filter also searches the torrent hash fields to make it easier to identify .parts files
Deluge
easier to identify .parts files
----------------------------+------------------------------------
Reporter: iconoclasthero | Type: feature-request
Status: new | Priority: minor
Milestone: needs verified | Component: Unknown
Version: 2.1.0 | Keywords: filter hash parts file
----------------------------+------------------------------------
^F/filter also searches the torrent hash fields to make it easier to
identify .parts files
While I think of ^F as "find," I noticed that the dialog box says filter.
In either case, identifying .part files can be a PITA and it would be
helpful if one could take the torrent hash from the .parts file and filter
for it.
Mentioned this on the deluge discord:
> iconoclast hero: so ^F opens the Filter dialog (I think of it as find).
Would "^F also searches the torrent hash fields to make it easier to
identify .parts files" be a reasonable feature request?
>
> ambiproDev: it would be reasonable request yea, whether it can be
implemented easily is another story, identifying if a search string is a
infohash in full would be pretty trivial
>
> ambiproDev: but if you're searching for like part of a infohash, you'd
have to basically just double the search base to include infohashes
>
> ambiproDev: prob not that big of a deal most of the time either though
The only other way I've been able to do this is by something like
{{{
#!/bin/bash
hash="$1"
for i in "$torrentdir"/*.torrent; do
showhash="$(/usr/bin/transmission-show "$i"|\grep -E Hash.+\:)"
showhash="${showhash#*: }"
[[ "$hash" = "$showhash" ]] && echo "$i"
done
}}}
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3646>
Deluge <https://deluge-torrent.org/>
Deluge Project
Deluge
easier to identify .parts files
Reporter: iconoclasthero | Owner: (none)
Type: feature-request | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: 2.1.0
------------------------------+------------------------------------
Description changed by iconoclasthero:
Old description:
> ^F/filter also searches the torrent hash fields to make it easier to
> identify .parts files
>
> While I think of ^F as "find," I noticed that the dialog box says filter.
> In either case, identifying .part files can be a PITA and it would be
> helpful if one could take the torrent hash from the .parts file and
> filter for it.
>
> Mentioned this on the deluge discord:
>
> > iconoclast hero: so ^F opens the Filter dialog (I think of it as find).
> Would "^F also searches the torrent hash fields to make it easier to
> identify .parts files" be a reasonable feature request?
> >
> > ambiproDev: it would be reasonable request yea, whether it can be
> implemented easily is another story, identifying if a search string is a
> infohash in full would be pretty trivial
> >
> > ambiproDev: but if you're searching for like part of a infohash, you'd
> have to basically just double the search base to include infohashes
> >
> > ambiproDev: prob not that big of a deal most of the time either though
>
> The only other way I've been able to do this is by something like
>
> {{{
> #!/bin/bash
>
> hash="$1"
>
> for i in "$torrentdir"/*.torrent; do
> showhash="$(/usr/bin/transmission-show "$i"|\grep -E Hash.+\:)"
> showhash="${showhash#*: }"
> [[ "$hash" = "$showhash" ]] && echo "$i"
> done
>
> }}}
New description:
Ctrl-F/filter also searches the torrent hash fields to make it easier to
identify .parts files
While I think of Ctrl-F as "find," I noticed that the dialog box says
filter. In either case, identifying .part files can be a PITA and it
would be helpful if one could take the torrent hash from the .parts file
and filter for it.
Mentioned this on the deluge discord:
> iconoclast hero: so ^F opens the Filter dialog (I think of it as find).
Would "^F also searches the torrent hash fields to make it easier to
identify .parts files" be a reasonable feature request?
>
> ambiproDev: it would be reasonable request yea, whether it can be
implemented easily is another story, identifying if a search string is a
infohash in full would be pretty trivial
>
> ambiproDev: but if you're searching for like part of a infohash, you'd
have to basically just double the search base to include infohashes
>
> ambiproDev: prob not that big of a deal most of the time either though
The only other way I've been able to do this is by something like
{{{
#!/bin/bash
hash="$1"
for i in "$torrentdir"/*.torrent; do
showhash="$(/usr/bin/transmission-show "$i"|\grep -E Hash.+\:)"
showhash="${showhash#*: }"
[[ "$hash" = "$showhash" ]] && echo "$i"
done
}}}
--
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3646#comment:1>
Deluge
easier to identify .parts files
Reporter: iconoclasthero | Owner: (none)
Priority: minor | Milestone: needs verified
Component: Unknown | Version: 2.1.0
------------------------------+------------------------------------
Description changed by iconoclasthero:
Old description:
> Ctrl-F/filter also searches the torrent hash fields to make it easier to
> identify .parts files
>
> While I think of Ctrl-F as "find," I noticed that the dialog box says
> filter. In either case, identifying .part files can be a PITA and it
> would be helpful if one could take the torrent hash from the .parts file
> and filter for it.
>
> Mentioned this on the deluge discord:
>
> > iconoclast hero: so ^F opens the Filter dialog (I think of it as find).
> Would "^F also searches the torrent hash fields to make it easier to
> identify .parts files" be a reasonable feature request?
> >
> > ambiproDev: it would be reasonable request yea, whether it can be
> implemented easily is another story, identifying if a search string is a
> infohash in full would be pretty trivial
> >
> > ambiproDev: but if you're searching for like part of a infohash, you'd
> have to basically just double the search base to include infohashes
> >
> > ambiproDev: prob not that big of a deal most of the time either though
>
> The only other way I've been able to do this is by something like
>
> {{{
> #!/bin/bash
>
> hash="$1"
>
> for i in "$torrentdir"/*.torrent; do
> showhash="$(/usr/bin/transmission-show "$i"|\grep -E Hash.+\:)"
> showhash="${showhash#*: }"
> [[ "$hash" = "$showhash" ]] && echo "$i"
> done
>
> }}}
New description:
Ctrl-F/filter also searches the torrent hash fields to make it easier to
identify .parts files
While I think of Ctrl-F as "find," I noticed that the dialog box says
filter. In either case, identifying .part files can be a PITA and it
would be helpful if one could take the torrent hash from the .parts file
and filter for it.
Mentioned this on the deluge discord:
> iconoclast hero: so `^F` opens the Filter dialog (I think of it as
find). Would "`^F` also searches the torrent hash fields to make it
easier to identify .parts files" be a reasonable feature request?
>
> ambiproDev: it would be reasonable request yea, whether it can be
implemented easily is another story, identifying if a search string is a
infohash in full would be pretty trivial
>
> ambiproDev: but if you're searching for like part of a infohash, you'd
have to basically just double the search base to include infohashes
>
> ambiproDev: prob not that big of a deal most of the time either though
The only other way I've been able to do this is by something like
{{{
#!/bin/bash
hash="$1"
for i in "$torrentdir"/*.torrent; do
showhash="$(/usr/bin/transmission-show "$i"|\grep -E Hash.+\:)"
showhash="${showhash#*: }"
[[ "$hash" = "$showhash" ]] && echo "$i"
done
}}}
--
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3646#comment:2>