unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: oitofelix@gmail.com (Bruno Félix Rezende Ribeiro)
Cc: 10787@debbugs.gnu.org
Subject: bug#10787: 23.4; hs-hide-* functions don't honor page break in Emacs-Lisp major mode (and probably others too)
Date: Fri, 01 Nov 2019 23:45:25 +0100	[thread overview]
Message-ID: <87mudfw70a.fsf@marxist.se> (raw)
In-Reply-To: <87vcnem34v.fsf@felix-laptop.gnung> ("Bruno Félix Rezende Ribeiro"'s message of "Sat, 11 Feb 2012 01:59:28 -0200")

oitofelix@gmail.com (Bruno Félix Rezende Ribeiro) writes:

> Suppose that you have a buffer with Emacs-Lisp major mode and hs minor
> mode enabled and into it a piece of code like this: (where ^L indicates
> page break)
>
> --
>
> ;; here is only a foo comment for a commented bar function
> ;; (defun my-bar-function () nil)
>
> ^L
> ;; here is another foo comment for another commented bar function
> ;; (defun my-second-bar-function () nil)
>
> --
>
> Now, if you run hs-hide-all command the text appears like this:
>
> --
>
> ;; here is only a foo comment for a commented bar function...
>
> --
>
> It's very annoying.  I often comment consecutive functions and
> hs-hide-all don't honor sequential newlines.  So, I was breaked page
> hoping that my functions were kept separated.  But that didn't happen.
> This bug report is to suggest developers to make hs-hide-* functions
> respect page breaks for this and others major modes too.

This was reported 7 years ago, but never got a reply at the time.

I can't reproduce this on current master.  Are you still seeing this
on a modern version of Emacs?

If I don't hear back from you within a couple of weeks, Ill just close
this bug as unreproducible.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-11-01 22:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11  3:59 bug#10787: 23.4; hs-hide-* functions don't honor page break in Emacs-Lisp major mode (and probably others too) Bruno Félix Rezende Ribeiro
2019-11-01 22:45 ` Stefan Kangas [this message]
2019-11-02  5:02   ` Stefan Kangas
2019-12-05 11:06   ` Stefan Kangas

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=87mudfw70a.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=10787@debbugs.gnu.org \
    --cc=oitofelix@gmail.com \
    /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).