From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Pierre Penninckx Newsgroups: gmane.emacs.devel Subject: auth-source-search regex/fuzzy/partial match Date: Fri, 21 Jun 2019 21:41:06 -0700 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="213384"; mail-complaints-to="usenet@blaine.gmane.org" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 22 06:42:10 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1heXqs-000tO3-DH for ged-emacs-devel@m.gmane.org; Sat, 22 Jun 2019 06:42:10 +0200 Original-Received: from localhost ([::1]:38974 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heXqr-0006bl-1J for ged-emacs-devel@m.gmane.org; Sat, 22 Jun 2019 00:42:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42654) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heXqT-0006bd-Uu for emacs-devel@gnu.org; Sat, 22 Jun 2019 00:41:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1heXqT-0008LO-68 for emacs-devel@gnu.org; Sat, 22 Jun 2019 00:41:45 -0400 Original-Received: from mail-ed1-x532.google.com ([2a00:1450:4864:20::532]:34449) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1heXqS-0008JL-Sw for emacs-devel@gnu.org; Sat, 22 Jun 2019 00:41:45 -0400 Original-Received: by mail-ed1-x532.google.com with SMTP id s49so13208653edb.1 for ; Fri, 21 Jun 2019 21:41:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pKRMLuFyh+e1fWwkGlpMMnFcDI4NbsCmBD/dfRu05n8=; b=pfpn/mlLg3ZDGhgTCfNYh5Ro/TZ+yd209Gvvgw1fkV6Rkbq2hBB+o5bYxQTuzVxUTg rDawT0KGquEQPQVwKXwdM9t71083vaH/B8tNK7QQzjblLpmSqP9UaVXk1wNvz+i8/oRr T4GZwlKDEiQuMaAEknGTAcKFPETjtRbxPupa8lKGWa8FVjxvnQSaCDrXhEsqhUsisEZv UKEEiS+2Cm926/Pks5kXyNbrhH3J544tdHqfjLEDcZLncYip97M5NImsvzF9vmFanRf3 iOJb2uvEHBGim4SD32OgybDvNSbMBontVGeQ3bhDLnskZE3dPrtsN5OODcpY7srdSDhG w1Xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pKRMLuFyh+e1fWwkGlpMMnFcDI4NbsCmBD/dfRu05n8=; b=qg3oDxqGNchd2QgJ27nje54hHe5BUg7WlkArIdWvxv+pyV3gPnRFjLAmRn/E7EKMXs 0dTGX5nGs06sCfRqIO5/3oYAp1Lk7fWM1TuXuOYp/gn81emcDh4QK4w46mt5qmhJjGuo blk4T5g/IVvAiAYR/iShnTrrU4eZv1cqv/7KOTWZwoLaIs9c4rjoYRbeaFUMxLj7nNNw 0lJ9Xl6HEGYWPWPni+djyvbVz+Cwbx+NZA4sNCyf5w83Sd1NU4/W0rhSmEJb00/yWL3q 5UzYRt8usx1ZY736TYOBTHiMUl0OFGV0oh3HHOU/OCKk1nHq342RbSkhKH4XjK6XTUAU MMnA== X-Gm-Message-State: APjAAAUV4VDl9rwxogUVR6NTGOEXkZbctwqQNdqOGX5DaBC/oabQz6R7 3GA1t6WkQU2HXSJ1ozVJyPk/bsrKNkRcuiqjMh6VfmAvaW0= X-Google-Smtp-Source: APXvYqzUqBc/IORAPzIYXLCHDcXbplruzL+jt60f4gKkQsgaJ9uvAD0c0ML2jQ/G44JsaqCWBeHvcHKn0xUnvm9r1yc= X-Received: by 2002:a17:906:1286:: with SMTP id k6mr83975628ejb.183.1561178502291; Fri, 21 Jun 2019 21:41:42 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::532 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:238018 Archived-At: Hello, I was wondering if some work was done already to allow for `auth-source-search' to return entries that partially match the given spec. I didn't find anything on this subject after a some research. For example, say `(auth-source-search :host "test" :max 10)' finds one match. I'd like `:host "tes"' or `:host "est"' to find that match too. If a backend provides something like this, it's by using some custom code circumventing `auth-source-search'. I'm thinking the best way to add this would be to enhance the `spec' argument from `auth-source-search' to take an additional `:regex' property. Or would adding a new function make more sense? Best, Pierre