I'd like to heartily endorse the inclusion of Marco's patch. (I just
debugged this today and came up with the same fix; then I found this
email.)
The patch is a very minor fix for a bug that detracts significantly from
bbdb functionality. Without the patch, bbdb-omit-record does not work,
since bbdb-redisplay-record is missing the delete-p argument. As a
result, when one calls bbdb-omit-record, instead of excluding the
current record, it instead redisplays the *BBDB* buffer with the current
record at the top of the buffer.
Thanks,
Matt
Marco Wahl <marcowahls...@gmail.com> writes:
> Hi Roland and all,
>
> Please consider to apply this microscopic patch for resurrecting
> `bbdb-omit-record' (which is on key 'o' in *BBDB*.)
>
>
> Best regards!
> --
> Marco Wahl
> GPG: 0x49010A040A3AE6F2
>
>>From 1e82d7d5d86a978619bbea52c23ba663d1747ced Mon Sep 17 00:00:00 2001
> From: Marco Wahl <marcowahls...@gmail.com>
> Date: Tue, 15 Dec 2015 22:53:22 +0100
> Subject: [PATCH] Fix bbdb-omit-record
>
> ---
> lisp/bbdb-com.el | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lisp/bbdb-com.el b/lisp/bbdb-com.el
> index c3fb500..d2f9a61 100644
> --- a/lisp/bbdb-com.el
> +++ b/lisp/bbdb-com.el
> @@ -1499,7 +1499,7 @@ With prefix N, omit the next N records. If negative,
> omit backwards."
>(setq n (min (- n) num))
>(bbdb-prev-record n))
> (dotimes (i n)
> - (bbdb-redisplay-record (bbdb-current-record) t
> + (bbdb-redisplay-record (bbdb-current-record) nil t
>
> ;;; Fixing up bogus records
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/