[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] Re: Limited #+INCLUDE ?
From: |
Eric Schulte |
Subject: |
Re: [Orgmode] Re: Limited #+INCLUDE ? |
Date: |
Tue, 27 Apr 2010 11:58:37 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
Dan Davison <address@hidden> writes:
> "Eric Schulte" <address@hidden> writes:
>
>> Darlan Cavalcante Moreira <address@hidden> writes:
>>
>>> This functionality would be really useful. Since it is more directly
>>> applicable for programming, then maybe an easier approach to implement it
>>> would be just a link to a function in a file. For instance
>>>
>>> [[file_def:/path/to/file::definition_name][linkname]]
>>>
>>> Org could rely on the capability of the target major-mode to select the
>>> region enclosing the function (c-mark-function for C/C++,
>>> py-mark-def-or-class for python, mark-defun for lisp, etc.). This would
>>> avoid the necessity of including commenting marks in the code and although
>>> it would be limited to a "function body at a time" it would be enough in
>>> many situations.
>>>
>>
>> Following in this "major mode specific behavior" direction, maybe it
>> would be possible to make use of the tags functionality for linking to
>> specific functions, chapters, etc... based on the mode of the target
>> file.
>
> This sounds like an interesting idea; I have been meaning to use tags
> more. However, I wouldn't want to exclude the possibility of using this
> functionality in a non-programming context
I agree that would be an unwelcome restriction, however maybe TAGS are
not restricted to programming text
,----[from (emacs) Tags ]
| A "tag" is a reference to a subunit in a program or in a document. In
| program source code, tags reference syntactic elements of the program:
| functions, subroutines, data types, macros, etc. In a document, tags
| reference chapters, sections, appendices, etc. Each tag specifies the
| name of the file where the corresponding subunit is defined, and the
| position of the subunit's definition in that file.
`----
also, they support general regexp tag specification through which they
can be extended to arbitrary major modes. -- Eric
> -- i.e. collaborative editing of arbitrary text documents -- which
> would argue for approaches based on storing arbitrary text context
> using Emacs bookmarks or custom text searches. Perhaps the new
> functionality could involve a choice of more than one new Org link
> type?
>
> Dan
>
>
>
>>
>> (info "(emacs)Tags") ;; how great is it that gnus resolves these links
>>
>> Tags would allow for robust links to points in changing files without
>> the need to place text anchors into the files themselves. The immediate
>> downside is that tags rely on a TAGS table to resolve links. This table
>> can easily be ignored from version control (for collaboration). Then
>> Org-mode could use the `find-tag' function to resolve it's links, maybe
>> in combination with the function delimiting features Darlan mentioned
>> above to references entire function/object ranges.
>>
>> -- Eric
>>
>>>
>>> Darlan
>>>
>>> 2010/4/27 Eric S Fraga <address@hidden>:
>>>> On Mon, 26 Apr 2010 15:40:35 -0400, Dan Davison <address@hidden> wrote:
>>>>> I'm considering investigating the following and would appreciate
>>>>> comments on this idea. The aim is to make it easier to use Org-mode to
>>>>> work pure code files which are *external to Org-mode* (i.e. this
>>>>> proposal lies outside of the current org-babel tangling framework).
>>>>>
>>>>> - Extend Org file links to allow links to a range of lines in a
>>>>> file. The syntax could be
>>>>> [[file:/path/to/file::from::to][linkname]]
>>>>
>>>> +1
>>>>
>>>> I like this idea, especially for exporting complex documents. If
>>>> org-store-link were enhanced to generate links with this line
>>>> information, I would probably use this a lot.
>>>>
>>>>> - These links will bring up a buffer visiting the target file, narrowed
>>>>> to the target region.
>>>>
>>>> Or could be brought up with a wide view but with the region selected?
>>>>
>>>>> - 'from' and 'to' could be line numbers, or regexps for text search.
>>>>
>>>> The latter could be quite appealing, although possibly a little
>>>> fragile.
>>>>
>>>>
>>>> _______________________________________________
>>>> Emacs-orgmode mailing list
>>>> Please use `Reply All' to send replies to the list.
>>>> address@hidden
>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- [Orgmode] Limited #+INCLUDE ?, Giles Chamberlin, 2010/04/23
- [Orgmode] Re: Limited #+INCLUDE ?, Sébastien Vauban, 2010/04/26
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Eric S Fraga, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Darlan Cavalcante Moreira, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Eric Schulte, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Dan Davison, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?,
Eric Schulte <=
- [Orgmode] Re: Limited #+INCLUDE ?, Giles Chamberlin, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Samuel Wales, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Dan Davison, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Carsten Dominik, 2010/04/27
- Re: [Orgmode] Re: Limited #+INCLUDE ?, Samuel Wales, 2010/04/29