unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jai-bholeki@gmx.com
To: jai-bholeki@gmx.com
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: problems with auto-fill-mode
Date: Sat, 30 Jan 2021 17:54:29 +0100	[thread overview]
Message-ID: <trinity-7f07c480-9f4d-4dfd-801e-85720e59dd67-1612025669331@3c-app-mailcom-bs16> (raw)
In-Reply-To: <trinity-2802f541-0dc1-4de2-af55-1338d695bc80-1612024604652@3c-app-mailcom-bs16>

Does it matter which expression to call first.

 (setq fill-column 72)
 (auto-fill-mode)

or

 (auto-fill-mode)
 (setq fill-column 72)


> Sent: Sunday, January 31, 2021 at 4:36 AM
> From: jai-bholeki@gmx.com
> To: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: problems with auto-fill-mode
>
> I am having a lot of problems on how to set up  auto-fill-mode.
>
> I want to cycle auto-fill of comments, then disable them using
> the keybinding "C-c q".
>
> Have written the following code.
>
> (defun break-comments ()
>   "Break lines when they exceed a specific character length."
>   (setq-local comment-auto-fill-only-comments t))
>
> (defun fill-break-comments ()
>   "Break lines when they exceed a specific character length."
>   (setq fill-column 72)
>   (setq-local comment-auto-fill-only-comments t)
>   (auto-fill-mode 0) )
>
> (defvar dfv-break-comments-state nil)
>
> ;; Cycles line breaking tool
> (defun cycle-break-comments ()
>   "Break comments in programming languages."
>   (interactive)
>
>   (pcase dfv-break-comments-state
>     ;;
>     (1 (setq-local comment-auto-fill-only-comments nil)
>        (auto-fill-mode 0)
>        (setq dfv-break-comments-state 0)
>        (message "%s" "Disable: Break comments"))
>     ;;
>     (_ (setq fill-column 72)
>        (if (not nil dfv-break-comments-state)
> 	   (add-hook 'prog-mode-hook #'break-comments)
> 	 (progn
> 	   (add-hook 'sh-mode-hook          #'break-comments)
> 	   (add-hook 'fortran-mode-hook     #'break-comments)
> 	   (add-hook 'emacs-lisp-mode-hook  #'break-comments)
> 	   (add-hook 'c-mode-hook           #'break-comments)
> 	   (add-hook 'c++-mode-hook         #'break-comments)
>            (add-hook 'awk-mode-hook         #'break-comments)
> 	   (add-hook 'R-mode-hook           #'break-comments)
> 	   (add-hook 'octave-mode-hook      #'break-comments)
> 	   ;;
> 	   (add-hook 'texinfo-mode-hook  #'break-comments)
> 	   (add-hook 'text-mode-hook     #'break-comments))
> 	 (auto-fill-mode))
>        ;;
>        (setq dfv-break-comments-state 1)
>        (message "%s" "Break comments using prog-mode-hook")) )
>
>   ;; Break comments using auto-fill
>   (global-set-key (kbd "C-c q") #'cycle-break-comments) )
>
>
>
>
>
>
>



  reply	other threads:[~2021-01-30 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 16:36 problems with auto-fill-mode jai-bholeki
2021-01-30 16:54 ` jai-bholeki [this message]
2021-01-30 17:04   ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-30 17:14     ` jai-bholeki

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=trinity-7f07c480-9f4d-4dfd-801e-85720e59dd67-1612025669331@3c-app-mailcom-bs16 \
    --to=jai-bholeki@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).