From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: ram Newsgroups: gmane.emacs.devel Subject: Re: question regarding my emacs package Date: Thu, 29 Jun 2023 19:28:42 +0000 Message-ID: <_IqK4pIWjfUFUTcXxOolJOvfrpuuofimCl0t1b-Y3MCnv4Y_F_iPKIKDQoHlKjyRNi3KxkmovDh7oYtf8-bb7mkRGm55JTeULhn9DjcFAXc=@rj95.be> References: <6cG8Tc55Zz8xk6rE6mJLfDxckAINPcYqp781yltsndzqq5146yw76EZ_2CoUtQT4P2j2afSx5VRD5G1-9qzFHWAW3LxYWwmxh87lvB2MgNE=@rj95.be> <2pOYRsmOk_f2sx48BICCjf9r3Z5OviLDonOFi4dhWoSpd_dAWOXFSA3jO2YeyJ5FBf-Sydd0ZTzTOsAlIg8tc_eBqM9nzq2PW4q4usn4Nuo=@rj95.be> <87ilbzkq9y.fsf@posteo.net> <877csetnwy.fsf@posteo.net> <87r0qbo29q.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40428"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, enometh@meer.net To: michael_heerdegen@web.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jun 30 07:28:47 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qF6gY-000AKV-R5 for ged-emacs-devel@m.gmane-mx.org; Fri, 30 Jun 2023 07:28:47 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qF6cg-0001R1-DC; Fri, 30 Jun 2023 01:24:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qExKP-0000Mh-KV for emacs-devel@gnu.org; Thu, 29 Jun 2023 15:29:17 -0400 Original-Received: from mail-0201.mail-europe.com ([51.77.79.158]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qExKC-0004yr-Au for emacs-devel@gnu.org; Thu, 29 Jun 2023 15:29:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rj95.be; s=protonmail3; t=1688066935; x=1688326135; bh=SfylaaLyGK/OQvl8VV5l118Ltixa+kU2cyFgW+Wk6ZI=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=UbetgU67VjCyJs95+ekj8XtmspFN10yvvQiIspAY/Jsds6mKidjBojrlsF8navV8x HWxlOfsK69IssDB6yapO0cDThEiqdElFuq8k7LM3scI8lvnespW+DlDABbNyvQ76LP pmkU3+QqQArQe5ccWoq30h6nDUz3O2SIGvexoOQtgmilWlPU1omQnDipYXAbYWYPEa dRJDlSwoik/oRseYkMxkPSoQheODmSSWqzbh/f7gBt8UnPxzl3HeTKvny0pKNnKUt6 7orywTjfJqWLU2CqHZQUcmo1EK5ZjxHzz3YB/DX3gCkRqwnM8e/Tn950LymFewB0fo YwxCjiIm4dwvw== In-Reply-To: Feedback-ID: 10803195:user:proton Received-SPF: pass client-ip=51.77.79.158; envelope-from=chat@rj95.be; helo=mail-0201.mail-europe.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Fri, 30 Jun 2023 01:24:21 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307308 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 got around to this. new repo is here:=C2=A0https://github.com/gitrj95/trail= .el renamed from breadcrumbs to trail, as per joao's suggestion, and changed th= e semantics quite a bit. i had some questions: - i'm supporting "middle" truncation of the file path strings. i couldn't= find this in emacs libs, but for this purpose, i found truncation at the s= uffix or prefix less useful than truncation in the middle. ie, i want to kn= ow the file name and extension almost always and the root directory (especi= ally in a code context) almost always - i'm using markers to track relative positions instead of absolute posit= ions. i found that, especially in the code context, i wanted the trail-mark= to "know" that i've added code before it, but still point to the function = prototype i marked before instead of sliding. markers don't seem to be pers= istable, so i had the absolute positions of the markers stored in the ring = that can be persisted, but default to corresponding markers in an associate= d, private ring if those exist. on hook for buffer close, the absolute posi= tions are updated with the marker details. this seems like a fairly common = thing to want to do, so i'd hope that i didn't reinvent the wheel. again, i= couldn't find anything also: - checkdoc passes - tested on emacs 27, 28, and 29 let me know if you have any questions, and please send over the fsf copyrig= ht agreement when you have the chance looking forward ------- Original Message ------- On Friday, June 16th, 2023 at 10:01 PM, ram wrote: > what versions does this impact? i=E2=80=99ve never run into this on >=3D2= 7.1? can someone confirm? >=20 >=20 >=20 > On Fri, Jun 16, 2023 at 10:28 AM, Michael Heerdegen wrote: >=20 > > Madhu writes: > >=20 > > > [Question about cl-defstruct] > >=20 > > > Debugger entered--Lisp error: (wrong-type-argument stringp > > > (buffer-file-name)) > > > make-breadcrumbs--breadcrumb--cmacro((make-breadcrumbs--breadcrumb)) > > > apply(make-breadcrumbs--breadcrumb--cmacro > > > (make-breadcrumbs--breadcrumb) nil) > > > macroexp--compiler-macro(make-breadcrumbs--breadcrumb--cmacro > > > (make-breadcrumbs--breadcrumb)) > > > ``` > >=20 > > @ram: AFAIU you need to use a different slot name. This one will cause > > problems due to a bug in Emacs. > >=20 > > Michael. -----BEGIN PGP SIGNATURE----- Version: ProtonMail wnUEARYKACcFgmSd21AJkLWF/Pp8PQPNFiEExUjWugOWGzBgCQZvtYX8+nw9 A80AACXgAQCVd483+cyNE+92uk5e8s6vlsWwUuDw33DfFpHQs4/tcAEApG0i 1FxxxcaK3wgFA0jZcTCAmlaTSWwi377MSkxzzgg=3D =3DOoeH -----END PGP SIGNATURE-----