Editing comments

Editing comments

[Andreas Röhler]

Hi,

commented code might need some edits too. In that case some basic 
commands like forward-sexp are not available.

Is there a minor-mode, un-commenting temporarily, writing back the result?

Thanks,

Andreas

Re: Editing comments

[Robert Thorpe]

Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> commented code might need some edits too. In that case some basic 
> commands like forward-sexp are not available.
>
> Is there a minor-mode, un-commenting temporarily, writing back the result?

What I do in this situation is I first mark the commented region.  I
then narrow to the region, then uncomment it, after that I widen.

So, something like:
* C-SPC
* M-} or M-C-f, etc
* C-x n n
* M-;
* Edit
* C-x h
* M-;
* C-x n w

There is probably a better way.

BR,
Rob

Re: Editing comments

[Andreas Röhler]

Am 05.06.2015 um 23:49 schrieb Robert Thorpe:
> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>> commented code might need some edits too. In that case some basic
>> commands like forward-sexp are not available.
>>
>> Is there a minor-mode, un-commenting temporarily, writing back the result?
> What I do in this situation is I first mark the commented region.  I
> then narrow to the region, then uncomment it, after that I widen.
>
> So, something like:
> * C-SPC
> * M-} or M-C-f, etc
> * C-x n n
> * M-;
> * Edit
> * C-x h
> * M-;
> * C-x n w
>
> There is probably a better way.
>
> BR,
> Rob

Thanks. IMO that's worth a minor-mode like wdired.

That would reduce needed keystrokes towards two - while marking comments 
already may cost severals.

Cheers,

Andreas

Re: Editing comments

[Javier]

>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>> commented code might need some edits too. In that case some basic
>>> commands like forward-sexp are not available.
>>>
>>> Is there a minor-mode, un-commenting temporarily, writing back the result?

You can always disable a block of code by an if(false).  The emacs
major mode will work fine that way and reactivating the code is just
changing 0 by 1.

Python
if(0):
    ...

C with preprocessor directives
#if 0
...
#endif

TeX
\iffalse
...
\fi

LaTeX with the comment environment in the verbatim package.
\begin{comment}
...
\end{comment}

Re: Editing comments

[Artur Malabarba]

> Thanks. IMO that's worth a minor-mode like wdired.
>
> That would reduce needed keystrokes towards two - while marking comments
already may cost severals.

I've never used it, but you might be looking for poporg. From their doc:

poporg is a small Emacs Lisp project to help editing program strings and
comments using Org mode (or any other major mode). This can be useful as it
is often more convenient to edit large pieces of text, like Emacs Lisp or
Python docstrings, in an org-mode buffer instead of in a comment or a
string.

Re: Editing comments

[Robert Thorpe]

Javier <nospam@nospam.com> writes:

> Python
> if(0):
>     ...

Yes, and for lisp you can use:

'(
...
)

BR,
Robert Thorpe

Re: Editing comments

[Andreas Röhler]

Am 07.06.2015 um 21:08 schrieb Artur Malabarba:
>
> > Thanks. IMO that's worth a minor-mode like wdired.
> >
> > That would reduce needed keystrokes towards two - while marking 
> comments already may cost severals.
>
> I've never used it, but you might be looking for poporg. From their doc:
>
> poporg is a small Emacs Lisp project to help editing program strings 
> and comments using Org mode (or any other major mode). This can be 
> useful as it is often more convenient to edit large pieces of text, 
> like Emacs Lisp or Python docstrings, in an org-mode buffer instead of 
> in a comment or a string.
>

Thanks for the hint,

Andreas

Re: Editing comments

[Phillip Lord]

lentic

You can use it to have two buffers one in (say) emacs-lisp and one is
(say) org-mode. You can edit either view and everything stays in sync.

The two buffers can be different -- so in the emacs-lisp view, all the
documentation is commented out, while in the org-mode view it is not.

Phil

Andreas Röhler <andreas.roehler@easy-emacs.de> writes:

> Hi,
>
> commented code might need some edits too. In that case some basic commands
> like forward-sexp are not available.
>
> Is there a minor-mode, un-commenting temporarily, writing back the result?
>
> Thanks,
>
> Andreas
>
>
>

-- 
Phillip Lord,                           Phone: +44 (0) 191 208 7827
Lecturer in Bioinformatics,             Email: phillip.lord@newcastle.ac.uk
School of Computing Science,            http://homepages.cs.ncl.ac.uk/phillip.lord
Room 914 Claremont Tower,               skype: russet_apples
Newcastle University,                   twitter: phillord
NE1 7RU                                 

Re: Editing comments

[Andreas Röhler]

Am 08.06.2015 um 16:24 schrieb Phillip Lord:
>
> lentic
>
> You can use it to have two buffers one in (say) emacs-lisp and one is
> (say) org-mode. You can edit either view and everything stays in sync.
>
> The two buffers can be different -- so in the emacs-lisp view, all the
> documentation is commented out, while in the org-mode view it is not.
>
> Phil
>
>

Cloned.

My usecase for lentic probably will be edits at different parts of 
buffer - while keeping the other part in view. Very interesting, thanks 
a lot!

Andreas

Re: Editing comments

[Phillip Lord]

Andreas Röhler <andreas.roehler@easy-emacs.de> writes:

> Am 08.06.2015 um 16:24 schrieb Phillip Lord:
>>
>> lentic
>>
>> You can use it to have two buffers one in (say) emacs-lisp and one is
>> (say) org-mode. You can edit either view and everything stays in sync.
>>
>> The two buffers can be different -- so in the emacs-lisp view, all the
>> documentation is commented out, while in the org-mode view it is not.
>>
>> Phil
>>
>>
>
> Cloned.
>
> My usecase for lentic probably will be edits at different parts of buffer -
> while keeping the other part in view. Very interesting, thanks a lot!


It's worth mentioning that there is an outstanding bug with that --
sometimes it loses the location of point. I know how to fix this, I
think, but have not had leisure. Let me know if it affects you, and I
will move it up the list.

Phil