unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: dptd dptd <dptdescribe@gmail.com>
Cc: 25565@debbugs.gnu.org
Subject: bug#25565: mark-whole-buffer and unnecessary (point) call
Date: Sun, 29 Jan 2017 20:48:52 +0100	[thread overview]
Message-ID: <8760kx4pgb.fsf@rosalinde> (raw)
In-Reply-To: <7AA23B8E-95A3-4BF4-AF53-AE1FD826D668@gmail.com> (dptd dptd's message of "Sun, 29 Jan 2017 15:27:22 +0200")

On Sun, 29 Jan 2017 15:27:22 +0200 dptd dptd <dptdescribe@gmail.com> wrote:

>> On 29 Jan 2017, at 12:41, Stephen Berman <stephen.berman@gmx.net> wrote:
>> 
>> On Sun, 29 Jan 2017 09:23:40 +0200 dptd dptd <dptdescribe@gmail.com> wrote:
>> 
>>>> On 29 Jan 2017, at 05:40, Eli Zaretskii <eliz@gnu.org> wrote:
[...]
>>>> If you type "C-x 4 a" inside every function, Emacs will format the
>>>> list for you, even if it's longer than a single line.  Then write the
>>>> description at the end.
>>>> 
>>> 
>>> I didn’t knew about this command! It’s awesome - thank you. However it isn’t
>>> breaking my lines when
>>> longer than 78 characters. :( I have tried from both - calling directly from
>>> the function source code
>>> and from the magit’s staged changes.
>> 
>> Do you have `fill-column' set somewhere?
>> 
>> Steve Berman
>
> Actually yes, I do.
>
> C-v fill-column
> --------
> fill-column is a variable defined in ‘C source code’.
> Its value is 70
> Local in buffer ChangeLog; global value is the same.
> --------

This is is the standard value in ChangeLog mode, so I don't know why you
aren't getting line-breaking.  You could check what happens when you
start Emacs with -Q, and if it works there, that means something in your
initializations, or a library you've loaded, is causing the problem.  In
that case, you can bisect your init file to find the culpable bit (i.e.,
comment out half of it, restart Emacs with the result, if the problem
still occurs, comment out half of the uncommented part and repeat,
otherwise reverse the commenting out and do the same).

> Here is the newest patch.
> --------
> From c869759f7d7fddb8f8b9fbd9fa7360b1d17edf57 Mon Sep 17 00:00:00 2001
> From: Bartosz Duszel <bartosz.duszel@gmail.com>
> Date: Sun, 29 Jan 2017 14:47:23 +0200
> Subject: [PATCH] Remove unnecessary argument `(point)' from calls to
>  `push-mark'.
>
> * lisp/textmodes/bib-mode.el (mark-bib):
> * lisp/simple.el (mark-whole-buffer, yank):
> * lisp/ses.el (ses--advice-yank, ses-mark-row, ses-mark-column):
> * lisp/progmodes/xscheme.el (xscheme-yank):
> * lisp/progmodes/verilog-mode.el (verilog-mark-defun):
> * lisp/progmodes/perl-mode.el (perl-mark-function):
> * lisp/progmodes/pascal.el (pascal-mark-defun):
> * lisp/progmodes/meta-mode.el (meta-mark-defun):
> * lisp/progmodes/icon.el (mark-icon-function):
> * lisp/progmodes/cc-cmds.el (c-mark-function):
> * lisp/obsolete/vip.el (ex-goto):
> * lisp/obsolete/vi.el (vi-put-before):
> * lisp/mouse.el (mouse-yank-primary):
> * lisp/menu-bar.el (menu-bar-select-yank):
> * lisp/mail/sendmail.el (mail-yank-original):
> * lisp/hexl.el (hexl-beginning-of-buffer, hexl-end-of-buffer):
> * lisp/emulation/viper-cmd.el (viper-mark-beginning-of-buffer):
> (viper-mark-end-of-buffer):

There should be no colon `:' after `(viper-mark-beginning-of-buffer)',
since `(viper-mark-end-of-buffer)' in the next line is in the same file.

> * lisp/cedet/semantic/senator.el (senator-mark-defun):
> * lisp/allout.el (allout-mark-topic): Remove unnecessary argument
> `(point)' from calls to `push-mark'.

Steve Berman





  reply	other threads:[~2017-01-29 19:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 15:33 bug#25565: mark-whole-buffer and unnecessary (point) call dptd dptd
2017-01-28 19:08 ` Eli Zaretskii
2017-01-28 21:24   ` dptd dptd
2017-01-29  3:40     ` Eli Zaretskii
2017-01-29  7:23       ` dptd dptd
2017-01-29 10:41         ` Stephen Berman
2017-01-29 13:27           ` dptd dptd
2017-01-29 19:48             ` Stephen Berman [this message]
2017-01-29 20:46               ` dptd dptd
2017-01-29 21:29                 ` Stephen Berman
2017-03-24  6:23                   ` dptd dptd
2017-03-24  7:23                     ` Eli Zaretskii
2017-03-24  7:29                       ` dptd dptd
2017-04-28  8:28                 ` Eli Zaretskii
2017-01-29 15:25         ` Eli Zaretskii

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=8760kx4pgb.fsf@rosalinde \
    --to=stephen.berman@gmx.net \
    --cc=25565@debbugs.gnu.org \
    --cc=dptdescribe@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).