unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Psionic K <psionik@positron.solutions>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Submitting Dslide to Non-GNU ELPA
Date: Thu, 20 Jun 2024 17:57:38 +0900	[thread overview]
Message-ID: <CADQMGAS_yhW=5=iaHZMgjt+gcnUa2Hb5NDShQFV1PenDvT2Saw@mail.gmail.com> (raw)
In-Reply-To: <874j9o599o.fsf@posteo.net>

> Has development stopped on org-tree-slide?  Or is this a proper fork?

Fork, but almost a ground-up rewrite.  Only the slide header
generation and related customize options are recognizable.

Before I decided on a complete rewrite, I submitted some changes to
org-tree-slide.  They are not in master:
https://github.com/takaxp/org-tree-slide/commits/develop

> Here are a few comment

On first pass, I find most changes agreeable and intend to clean out
behaviors that lead to my versions.  Did you use a tool to scan for
these changes?



  reply	other threads:[~2024-06-20  8:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  6:02 Submitting Dslide to Non-GNU ELPA Psionic K
2024-06-20  8:05 ` Philip Kaludercic
2024-06-20  8:57   ` Psionic K [this message]
2024-06-20 13:28     ` Philip Kaludercic
2024-06-20 16:16       ` Psionic K
2024-06-20 17:53         ` Philip Kaludercic
2024-06-20 23:34           ` Psionic K
2024-06-21  5:55             ` Philip Kaludercic
2024-06-21  6:06               ` Psionic K
2024-06-21  6:59                 ` Philip Kaludercic
2024-06-21  8:55                   ` Psionic K
2024-06-21 13:42                     ` Psionic K
2024-06-21 15:04                     ` Philip Kaludercic
2024-06-22  0:47                       ` Psionic K
2024-07-02 15:41                         ` Psionic K
2024-07-07 21:26                           ` Philip Kaludercic
2024-08-12 17:20                           ` Philip Kaludercic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADQMGAS_yhW=5=iaHZMgjt+gcnUa2Hb5NDShQFV1PenDvT2Saw@mail.gmail.com' \
    --to=psionik@positron.solutions \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).